Skip to content

Instance Details Status Tab

Select the Status tab to open a graphical representation of the instance.

The graph represents the runtime execution of the journey built in the Relationships tab of the journey details. Each point represents a component in the journey that receives events during the instance.

Use the Zoom tools to resize the graph. Click to open a component-type legend.

Batch pipeline details

For batch pipeline components, each node includes the component name; the number of runs that occur during the instance and a summary of their statuses; and a summary of tests that occur during the instance.

Each batch pipeline node shows an overall status that represents the highest severity run status and test outcome. The status considers when:

  1. At least one run fails.
  2. At least one test fails.
  3. At least one run is missed.
  4. At least one run is completed with warnings.
  5. At least one test is completed with warnings.
  6. There is a pending run.
  7. The run is in progress (Running).
  8. All runs are completed without issue.
  9. All tests pass.

For example, if a batch pipeline has two runs during the instance, with statuses "completed" and "completed with warnings," and one failed test, the overall node status is "failed."

Go to Batch Runs

From the Status tab, click the <x> runs link of any batch pipeline component to navigate to the Batch Runs tab. The runs shown in the list will be automatically filtered for that batch pipeline.

Dataset details

For dataset components, each node includes the component name; a summary of tests that occur during the instance; and the number of Dataset Operation write events received.

Each dataset node shows an overall status that represents the highest severity test outcome and Dataset Operation write event. The status considers when:

  1. At least one test fails.
  2. At least one test is completed with warnings.
  3. At least one write event is missed.
  4. All write events arrive.
  5. All tests pass (and at least one write event occurs).
  6. All tests pass, but no arrival window is set and no write event occurs.
  7. No tests occur, no arrival window is set, and no write event occurs.

For example, if a dataset receives a write event that misses its arrival window and has one failed test, the overall node status is "failed."

Server details

For server components, each node includes the component name and a summary of tests that occur during the instance.

Each dataset node shows an overall status that represents the highest severity test outcome, where failed > had warnings > passed.

DAG behaviors

At this time, an instance DAG is a direct reflection of the journey it belongs to. If you make a change to the layout of a journey, that change will be reflected in the Status DAG for current, and historical, instances.

For example, if you add a new component to a journey in the Relationships tab, all of the instances of that journey will now include that component. However, that component would not have existed at the time of the instance and will appear in the instance DAG with a status of "missed."

Visual example in Observability

(Screenshot of the Status tab)

Troubleshooting: Journey Sequence Not Met