Skip to main content
Use Prophecy’s built-in scheduler to automate pipeline runs based on time or file triggers. You can create multiple schedules for a single pipeline, each with its own configuration including parameter sets, triggers, and alerts.

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:
  1. Open a pipeline in the project editor.
  2. Expand the … menu in the pipeline canvas header.
  3. Click Schedule.
  4. To create a new schedule, click New Schedule. To edit an existing schedule, select it from the schedules list.
  5. 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.
  6. Expand the Choose Pipeline Parameter Set dropdown and select the pipeline parameter set you want to use for this schedule.
  7. Configure the trigger for the schedule.
  8. Optionally, set up an email alert in your schedule.
  9. Click the On toggle to enable the schedule.
  10. Click Schedule to save the schedule.
You can create multiple schedules for the same pipeline, each with different parameter sets, triggers, and timing configurations. This allows you to run the same pipeline with different settings at different times or frequencies.

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:
  1. Open a pipeline in the project editor.
  2. Expand the … menu in the pipeline canvas header.
  3. Click Schedule.
  4. Select the schedule you want to delete.
  5. Click Delete Schedule.
  6. Click Delete to confirm the deletion.
When you delete a schedule, you still have to publish the project for the changes to take effect in the deployed pipeline.

What’s next

Once you have set up your schedules: