Get a schedule
Authentication
Basic authentication of the form Basic <base64(username:password)>.
Path parameters
The schedule’s unique identifier (triggers._id), a UUIDv7.
Response
The user who created the schedule. principalId is Pronghorn when no creator is recorded.
When the schedule was last changed by a user (an edit, a pause or a resume), ISO 8601 in UTC.
active fires as scheduled; paused was stopped by a user; completed fired its last occurrence; expired ended without firing its last occurrence.
recurring repeats on its schedule; concrete fires once, at concreteDate.
What happens to an occurrence found overdue, such as after downtime: skip drops it and waits for the next one; fireOnce fires it, however late.
Legacy field, kept only to support workflows written for the old input shape: before July 2023, Operations Manager passed form values to the workflow inside one variable named formData. False unless it was turned on.
How a recurring schedule repeats, and its start and end. Absent for a concrete schedule.
The instant a concrete schedule fires, ISO 8601 in UTC. Set only when scheduleType is concrete. A request sets it as schedule.concreteDate.
When the schedule is next due, ISO 8601 in UTC. Present only while the status is active.