Run a batch pipeline on a schedule

So far, you have started the batch pipeline yourself with Run now. When the same job must run every day or every week, you can save a recurring schedule on the pipeline.

In this lesson, you schedule the pipeline from the previous lesson and observe how manual runs and stopping work.

Before you begin

The schedule in this lesson is available for a batch pipeline. If the pipeline has not been saved, select a collection and select Save first.

Confirm that the top bar shows:

• the pipeline status;
• recent runs as a small run-history bar;
• the Settings icon; and
• the Run now button.

Add a recurring schedule

1. Select the Pipeline Settings icon in the pipeline's top bar.
2. Open the Schedule tab.
3. Turn on Enable Schedule.
4. Select Daily and choose a run time. For this lesson, use a time that does not overlap another job.
5. Review the generated schedule summary and select Save.

The current editor offers Every minute, Hourly, Daily, Weekly, and Monthly presets. It stores the selected recurrence as a five-field cron expression.

A pipeline imported or updated through the API may already contain an RRULE schedule, which appears as an RRule schedule badge. The current screen does not edit that advanced expression directly. Saving a new preset from the Schedule tab replaces it with the new cron schedule.

Confirm that the schedule is active

After closing Settings, a schedule badge appears in the top bar and the pipeline status changes to indicate that its schedule is active. The schedule takes effect after it is saved.

An automatic run begins only when its scheduled time arrives. To check the pipeline immediately, use Run now. Starting one manual run does not remove the recurring schedule.

Run now and observe the state

1. Select Run now.
2. Confirm that the button changes to Stop and the status shows that the pipeline is running.
3. Watch the code node's state change on the canvas.
4. When the run finishes, confirm that a new result appears in the run-history bar.

Run-history colors let you distinguish recent successful, failed, and active runs. Select a code node and open the inspector's History tab to see that node's run state and duration.

Understand Stop

While a batch pipeline is running, the top bar shows Stop. Selecting it requests that the current run stop.

Stop does not immediately cancel every task or roll back output that has already been written. The run stops at the next boundary between concurrently executed step groups, so output from completed steps can remain. After investigating the cause, run the full pipeline again to restore a consistent result.

Change or remove a schedule

• To change the recurrence, choose a new value under Pipeline Settings → Schedule and save it.
• To disable automatic runs, turn off Enable Schedule and save.
• A pipeline without a schedule can still be started with Run now.

This screen does not provide email, Slack, Webhook, or escalation-policy settings. If operations alerts are required, follow the monitoring process used by your organization.

Self-check

• Did you save the batch pipeline before opening the Schedule tab?
• Did you verify the run time in UTC?
• After saving, do the schedule badge and active-schedule status appear?
• Does a new result appear in run history after Run now?
• Do you understand that Stop does not roll back completed output?

Next lesson

In the final lesson, you deliberately introduce a code error and inspect it in History. You then restore the code, run the full pipeline successfully, and prepare the dataset information that an analyst needs for handoff.