Skip to content

Configure an Expected Schedule

You can set a schedule for when you expect runs to start and/or end for batch pipeline components.

Observability can then generate Pending and Missing statuses and timeliness indicators to report when these expectations are not met.

Expected behaviors

Expectations are evaluated for the batch pipeline component and for any journeys that include the component.

You can monitor the following process from the Batch Runs tab of the Events page and instance details.

  1. On the day and/or time set by the Expected Start Time, the system verifies the batch pipeline component is receiving events.

    Note

    The system performs its verification after the grace period.

    • If the batch pipeline is running, the run status is set to Running. The system continues with step 2.
    • If the pipeline hasn't received an event, a placeholder run is created with the status Pending and a late start indicator with the expected start time. The system continues with step 2.

  2. For each journey that includes the component:

    • If there is an active instance for a journey, the system associates the run with that instance.
    • If there is no active instance for a journey, the system creates a new instance. The run is associated with the new instance.

  3. As run events are—or are not—received, the system updates the run and instance to inform you of progress relative to the expectation.

  4. On the day and/or time set by Expected End Time, the system verifies the status of the run.
    • If the run is still in progress, a late-end indicator displays with the expected end time.
    • If no run occurs by the next expected start, the run status is set to Missing.

How to

You can set an expected start and/or end schedule for batch pipeline components.

The following describes how to make changes to a single component. To update multiple components at once, see Bulk Component Actions.

Tip

Use Custom cron expressions in your expectations. See Cron Expressions in Observability for what's supported.

  1. Use one of the following to navigate to the component details:
    • Select Components from the menu, then select a batch pipeline.
    • Select Journeys from the menu, then select a journey that includes a batch pipeline. From the Relationships tab, click .
  2. Click Edit.

  3. Optional. Under Expected Schedule, set an expected start time.

    1. Click in the Starts field.
    2. Select the timeframe: Every x hours, Every x days, On certain days, or Custom.
    3. Complete the schedule details.
    4. Assign a timezone.
    5. Verify that the Next Time calculated by the system aligns with your expectations. Make adjustments as needed.
    6. Click Apply.

  4. To set a start time Grace Period:

    1. Click in the first field.
    2. Enter a whole number to represent the window of time.
    3. User the drop-down to set the unit: minutes, hours, or days.

  5. Optional. Set an expected end time.

    Note

    If only an end schedule is set, the system checks the expectation against the batch pipeline's most recent run.

    1. Click in the Ends field.
    2. Select the timeframe: Every x hours, Every x days, On certain days, or Custom.
    3. Complete the schedule details.
    4. Assign a timezone.
    5. Verify that the Next Time calculated by the system aligns with your expectations. Make adjustments as needed.
    6. Click Apply.

  6. Click Save.

At any point, click Cancel to end without saving.

Troubleshooting: Pending or Missing Runs