Skip to main content

​
The list

The Schedules page lists schedules grouped by destination, with these columns: Destination, Schedule, Status, Result, Project, Frequency, Author, the last execution and the next execution.
Schedules list expanded for Contract routing, with one Ended schedule with a Completed result and one Active weekly schedule
Use the search box to find a destination by name, the filters Status, Project and Created, and the sort options Most recent, Name and Next execution. The counter Needs attention shows schedules whose latest run failed or could not start.

​
Statuses

​
Open a schedule

Click a row to open its details. The dialog has two tabs.
  • History lists every time the schedule fired.
  • Configuration is the same form you used to create it. Change what you need and click Save changes.
Details of the finished one-time schedule, History tab, with the Completed run and the links View in Usage and View in Debug
Configuration tab of an active weekly schedule, with name, destination, frequency, time zone and inputs

​
History

Each entry shows the scheduled time, the status and when it was dispatched. For runs that started, the links View in Usage and View in Debug open the run itself, where you read the result like any other run.

​
Pause, resume, edit and delete

  • Pause stops new runs. Runs that were already prepared can still execute.
  • Resume continues from the next due time. Runs missed while it was paused are not replayed.
  • Edit in the Configuration tab changes the name, the frequency, the time zone, who can see it and the inputs. A change applies from the next run. The inputs you save replace the previous ones as a whole.
  • Delete cancels the runs that were waiting. Runs already dispatched go on, and the history stays in Usage.

​
When a run fails

Most failures are one of two kinds. They look different in the history. The run never started (Failed to dispatch). The schedule could not hand the run to the destination. The usual causes are:
  • The inputs no longer match the published version, for example a variable was renamed or became required.
  • The schedule’s owner lost access to the destination.
  • A service was unavailable at that moment.
Open the Configuration tab, fix the inputs and save. The run started and failed (Failed). This is an ordinary failed run. Open it with View in Usage or View in Debug and investigate it as you would any other.
A recurring schedule that keeps failing is paused automatically and its creator is notified. After you fix the cause, click Resume.

​
Checklist before scheduling

  • The destination is published and you tested the version that is in Production (Agent: the published version).
  • The inputs saved on the schedule are the ones you want on every run.
  • The time zone is the one of the people who expect the result.
  • The frequency is as slow as the work allows, because every run spends credits.