Skip to main content
Open a schedule from the Schedules list to see its configuration, pipeline, run statistics, and full run history.

​
Overview

The header shows the schedule name, its latest status, and when it last ran. A metadata row shows the Git branch, trigger, cron, owner, integrations, SLA, and self-healing. Actions (subject to your permissions):
  • Run triggers a manual run.
  • Edit changes the schedule’s configuration. See Schedule Anatomy.
  • Clone duplicates the schedule as a starting point for a new one.

​
Pipeline

The pipeline shows the schedule’s commands. Switch between:
  • Graph: the commands and their order.
  • Timeline: the commands over time.
Go to Radar opens the schedule in Radar for cost and performance monitoring. The stats panel shows the Success %, Errors, and total Runs.

​
Merge queue

For an on-merge schedule set to Wait in line, a Merge queue card under the pipeline shows the merge whose run is in progress and the merges waiting, next first, each with its pull request, commit, and when it joined. It refreshes every 30 seconds.
  • Remove takes a merge out of the queue, and its steps are skipped. You need permission to run the schedule.
  • Run now starts a waiting merge out of turn. You need permission to edit the schedule.
See Merge queue.

​
Trigger a run manually

Click Run to start a run immediately, regardless of the schedule’s trigger. Manual runs appear in the run history like any other run.

​
Run history

The Run history table lists every run of the schedule: Click a run to open its run details.