This article covers:
|
In short
The Diagnostics Dashboard is a read-only view in the Segment Automation page that shows whether your data is moving correctly through two stages: Ingestion (data coming in) and Automations (segments automatically created).
Overview: The Two Stages
Every automation you run depends on a chain of steps working in order. Data has to arrive in the platform, and automations have to fire on schedule. When something feels off, the hard part has historically been knowing which stage to look at, and the answer usually meant asking your CSM or waiting on a support reply.
The Diagnostics Dashboard makes that chain visible to you directly. It's organized around the same two stages your data actually flows through:
Ingestion: Is your source data arriving and refreshing on schedule?
Automations: Are your automations running as expected?
Think of it as a set of checkpoints along a pipeline. If water isn't coming out the far end, the dashboard tells you which checkpoint to inspect rather than making you take the whole pipe apart.
The dashboard is read-only. It's there to give you visibility, so you can't trigger, cancel, or change any ingestion cycle or automation from this view.
How It Works
Each stage runs on its own cycle. Ingestion refreshes bring data in, and automations fire on their schedules, each independently.
The dashboard records the last completed run. After a cycle finishes, its row updates with a status pill and a timestamp reflecting that most recent completed run.
Statuses update automatically. You don't refresh or configure anything. Once a cycle completes, the relevant section reflects it. A run that's still in progress mid-cycle continues to show the previous completed run's status until the new one finishes.
Failed statuses stick until resolved. A Failed pill persists until the next successful run of that same item completes. It does not clear just because a retry has started.
Where to Find It
1. Open the Segment Automations page in the platform.
2. The Diagnostics Dashboard appears at the top of the page within this view.
Reading the Status Pills
Each section uses color-coded pills. The available pills differ slightly by stage, so here's what each one means.
Ingestion
Shows every active data source with its last refresh timestamp and a status pill.
Pill | Meaning |
The most recent ingestion completed and added or updated data. | |
The ingestion completed but returned 0 new or updated rows. | |
The ingestion did not complete successfully. | |
(no pill) | This source has never completed an ingestion cycle yet. |
Automations
Shows every active automation with its last run timestamp and a status pill.
Pill | Meaning |
The automation ran as expected. | |
The automation run did not execute because the segment resolved to 0 fans. | |
| The automation run did not complete successfully. Persists until the next successful run. |
(no pill) | This automation has never run yet. |
What Shows Up on the Dashboard
Only active items appear. Active data sources and active automations are both represented.
Removed items drop off. If a data source is deactivated, or an automation is completed or deleted, it no longer appears on the dashboard.
Still Have Questions?
If a status looks wrong or a Failed pill isn't clearing after a successful cycle, reach out to support@stellaralgo.com. It helps to have ready: the section (Ingestion or Automation), the name of the source or automation, the timestamp shown on the pill, and any recent changes to that item.