Skip to content

Configure Default Instance Conditions

You can define the start and end of a journey's instances by the default behavior.

Summary of behaviors

Start a new instance

If there is no instance currently active for a journey, Observability starts a new instance when it receives the first event for any component included in that journey. If the component is included in several journeys, an instance starts for each journey that does not have an active instance.

You can specifically select the default start condition for a journey. That is, you can choose not to have a batch or schedule start condition.

End an active instance

There are two types of end conditions that apply by default:

  • Observability ends an active instance when each batch pipeline component in the journey has received a Run Status event with a run_status of "completed," "completed with warnings," or "failed."
    • This default behavior only applies if no start or end batch or schedule instance condition is configured.
  • Observability always ends an active instance when a new instance starts for the same journey, per any start condition.

Note

Default end conditions do not need to be configured to apply.

How to

To set instance conditions for a journey that's already been created, follow the steps below. Note that instance conditions can also be set during journey creation.

  1. Select Journeys from the menu > choose a journey from the list > select the Settings tab.
  2. Under Instance Conditions, click Edit journey instance conditions.
  3. Under Start a new instance, select Default only.
  4. Click Save.

At any point, click Cancel to end without saving.

How to change a start condition

From the journey details Settings tab, click Edit journey instance conditions under Instance Conditions.

Select a different start condition type and configure the details. Then, click Save.