Prerequisites
To leverage the built-in scheduler, your project must use the Simple Git Storage Model. Prophecy’s built-in scheduler does not appear in projects that use the Normal Git Storage Model.Configure a schedule
To configure a schedule for a pipeline:- Open a pipeline in the project editor.
- Expand the … menu in the pipeline canvas header.
- Click Schedule.
- To create a new schedule, click New schedule. To edit an existing schedule, select it from the schedules list.
- In Choose Pipeline Parameter Set, select a pipeline parameter set you want to use for this schedule.
- Set a Concurrency Policy for the schedule: Skip, Queue, or Cancel. See Set a concurrency policy below.
- Under Trigger, configure the trigger for the schedule.
- Under Which version runs, choose whether the schedule always uses the latest published version or locks to one specific version. See Lock a schedule to a version below.
- Optionally, set up an email alert in your schedule. You can also choose to run data quality Tests as part of the schedule.
- Click the switch next to the schedule name to enable the schedule.
- Click Save.
- In the confirmation dialog, click Publish Now to publish the project and activate the schedule, or click Later to publish another time.
Set a concurrency policy
The Concurrency Policy setting controls what happens when a scheduled run is due to start while the previous run of the same pipeline is still in progress. Concurrency policies apply only to time-based schedules, not to file arrival triggers. For example, suppose you schedule a pipeline to run every hour, on the hour. The 5:00 PM run is slow and doesn’t finish until 6:30 PM, so the 6:00 PM run comes due while the 5:00 PM run is still in progress. The concurrency policy determines how Prophecy handles the 6:00 PM run:
Schedules that don’t have a concurrency policy set use Queue. Queue holds at most one waiting run. If a long run overlaps several time slots, Prophecy starts one late run when the long run finishes, not one run for each missed slot.
Consider Skip or Cancel when a pipeline can take longer to run than the interval between scheduled runs. For example, if a pipeline takes 20 minutes but is scheduled every 5 minutes, Queue causes each run to start as soon as the previous one ends, so the pipeline runs back to back indefinitely.
The policy you choose affects how runs appear in Observability:
- Cancel: The stopped run appears with a Cancelled status rather than as a failure, and no failure alert is sent.
- Skip: A skipped time slot doesn’t create a run record.
If Prophecy can’t cancel the in-progress run, the schedule falls back to Queue behavior for that run.
Lock a schedule to a version
By default, a schedule always runs whichever version of the project is currently published. That is, when the team publishes a new version, the schedule automatically moves to this version for the next run. You can instead lock a schedule to one specific published version, so the scheduler keeps running that version no matter how many times the project is republished. To change or remove a lock, open the schedule and update Which version runs:- Select Always the latest published to unlock the schedule and have it follow future publishes again.
- Select Lock to a specific version and choose a different version to move the lock forward.
A locked schedule that’s already running a locked version is unaffected by publishing. Publishing makes no change to it until you update the lock yourself.
Locks apply per fabric. The same schedule can be locked to a version on one fabric’s deployment while following the latest published version on another.
Activate schedules
Enabling a schedule does not automatically activate it. To activate your schedules, publish the project. When you publish a project, Prophecy deploys all enabled schedules to your selected fabrics. In other words, your scheduled pipelines will begin running in the fabrics you selected. Any time you make changes to a schedule (including enabling, disabling, or editing the configuration), you must republish the project for those changes to take effect.Delete a schedule
To delete a schedule:- Open a pipeline in the project editor.
- Expand the … menu in the pipeline canvas header.
- Click Schedule.
- Select the schedule you want to delete.
- Click the trash icon next to the schedule name.
- Click Delete schedule to confirm the deletion.
- Click Save.
What’s next
Once you have set up your schedules:- Monitor automated pipeline runs in the Observability interface.
- Set up email alerts to stay informed about your scheduled pipeline runs.
- Learn more about different trigger types.

