Skip to main content
Retrieve details of a specific schedule.

POST /revisions/:id/data/query (Command: get_schedule)

Request Body

Response

See Alias Grammar to tell the schedule’s own alias apart from invocation_target.workflow_alias, and to see which commands accept a name in place of an id.

Errors

A caller cannot tell these two 403 cases apart — a schedule that does not exist and one that is not reachable both answer forbidden. Sessions already work this way; see Close Session.

Example

Alias resolution reads a secondary index that is eventually consistent, so an alias assigned moments earlier may not resolve yet. Hold the id returned by create_schedule rather than re-resolving the schedule by alias on every call.