Skip to main content
Create a new schedule in the scheduler blob revision. The schedule is registered with the underlying scheduling service immediately and begins firing according to its configuration once it becomes active.

POST /revisions/:id/data/command (Command: create_schedule)

Request Body

The schedule’s own alias names the schedule itself. It is unrelated to invocation_target.workflow_alias, which names the separate workflow definition the schedule invokes when it fires — the two keys sit side by side below but identify different objects.

Response

The schedule records the user_id of the user who created it. Scheduled executions this schedule triggers run as that user — which is what lets those executions, and any writes they make, be attributed back to a real identity.

Errors

Example (Recurring Cron)

Example (One-Time)