rebase workflow schedule
Manage workflow cron schedules.
Synopsis
rebase workflow schedule show <name> --project <project>
rebase workflow schedule set <name> --project <project> --cron "0 15 * * *" [--timezone <tz>] [--day-and] [--inactive] [--start <time>] [--end <time>]
rebase workflow schedule pause <name> --project <project> [--until <time> | --for <duration>]
rebase workflow schedule resume <name> --project <project>
rebase workflow schedule trigger <name> --project <project> [-p key=value] [--wait]
rebase workflow schedule clear <name> --project <project>
rebase workflow schedule list [--project <project>]Name-based lookup requires --project; every subcommand also accepts --id <uuid> instead of a name.
Subcommands
| Subcommand | Description |
|---|---|
show | Show a workflow's cron expression, timezone, window, active state, next run time, and the last skipped fire with its reason. |
set | Set or replace the workflow's cron schedule. |
pause | Stop the schedule from firing while keeping it registered, indefinitely or until a set time. |
resume | Re-activate a paused schedule. |
trigger | Trigger a run of the deployed workflow now, outside the schedule. |
clear | Remove the schedule. |
list | List all workflows that have schedules, with next run times. |
Options for set
| Option | Type | Description |
|---|---|---|
--cron | str | Five-field cron expression, e.g. "0 15 * * *". Required. |
--timezone | str | IANA timezone the expression is evaluated in, e.g. Europe/Stockholm. |
--day-and | bool | Require day-of-month AND day-of-week to match (default is standard cron OR). |
--inactive | bool | Register the schedule paused. |
--start | time | First fire at or after this date or ISO 8601 time, e.g. 2026-09-16. A bare date is the start of that day in --timezone. |
--end | time | No fire at or after this date or time (exclusive). Refused when already in the past. |
Options for pause
| Option | Type | Description |
|---|---|---|
--until, -u | time | Resume automatically at this time, e.g. 2026-09-15 or an ISO 8601 timestamp. A bare date or time is read in your local timezone. |
--for, -f | duration | Resume automatically after this long, e.g. 90m, 12h, 3d, 2w. |
Without either option the schedule stays paused until an explicit resume.
rebase workflow pause and rebase workflow resume are aliases for these two subcommands.
Options for trigger
| Option | Type | Description |
|---|---|---|
--param, -p | name=value | Run parameter. Values are parsed as JSON when possible. Repeat for multiple parameters. |
--parameters-json | json | JSON object with run parameters. |
--wait / --no-wait | bool | Follow the run until it finishes. Defaults to --no-wait. |
--timeout | int | Maximum seconds to wait with --wait. Defaults to 600. |
Behavior
--start and --end are part of the schedule definition, so setting them creates a workflow version like any other schedule change. Fires outside the window are skipped, and the first fire at or after --end switches the platform schedule off for good; list shows the state as starts …, active, ends …, or ended ….
Pausing is operational state on the workflow, not part of its schedule definition — it never creates a workflow version. While paused, the schedule stays registered but no runs fire, and each skipped fire is a skip, not a failure. A timed pause (--until/--for) lifts itself: the first fire at or after the expiry runs normally, and next_run_at reports that resume-time fire while the pause holds. Disabling the workflow itself (enabled=false) removes the schedule registration entirely.
Runs created by trigger carry trigger_source: "api"; runs fired by the cron schedule carry trigger_source: "schedule".

