Journey Sequence Not Met¶

The following banner appears in Observability to alert you:

Journey sequence not met. View timeline for more details.

Visual example in Observability¶

(Error banner for out of sequence journey)

Details¶

When you open the status tab of the instance details to view the progress of an instance, the banner informs you that this instance does not align with its journey.

An instance is the runtime execution of a journey, which is a collection of components in your data estate, as specified by you. When the system receives events from components that are included in a journey, the events become part of an instance.

The system evaluates the start and end events of batch pipeline runs against a journey's sequence. During an instance, if batch pipeline components execute their runs in a different order than the order set in the journey's sequence, the system generates this alert.

Example

For example, the journey above has three batch pipelines with runs expected in the order A > B > C. During an instance, if the runs execute in the order B > A > C, an alert would be generated.

Potential causes¶

There are several reasons why a journey's sequence is not met during an instance. For example:

There is a dependency issue among your components.
There is an order-of-operations issue in one of your batch pipelines.
Certain inputs or timings are incorrect in a batch pipeline.
The journey you've built is not reflective of your data estate.

Solution¶

Hover your cursor over the banner to see which batch pipeline components ran out of sequence. Then, to investigate the issue further, click the link included in the banner. You'll be redirected to the Timeline tab, where you can analyze the timings of potentially problematic or root cause components.

When you have enough information:

Make changes and adjustments in your data estate, so your components execute in the order you want them to.
Or, change the sequence of the journey to more closely align with the realities of your data estate. See Create Relationships for more information.

Afterward, watch subsequence instances of this journey to make sure the improvements you've made have the right effect.