Start a schedule's workflow now
Requires an Idempotency-Key, which names the run (400 idempotency_key_required without one). A repeat with the same key replays the stored 201 with Idempotent-Replayed: true. As StartRun, the app must serve the workflow now: 409 workflow_not_announced on a pull app no worker announced it to in the last 10 minutes, 409 app_not_synced or workflow_not_synced on a push app. Ignores the overlap policy and doesn't count as a firing. The caller also needs workflows.runs.start on the workflow.
https://workflows-api.ezghcloud.com/v1/organizations/{orgId}/projects/{projectId}/schedules/{scheduleId}/triggerAuthorization
Path parameters
Header parameters
Returns
200
The run this Idempotency-Key already started, once the key's stored answer has expired (48 h).
201
The new run.
400
invalid_request (with issues), invalid_cursor, or the endpoint's own 400 codes.
403
access_denied: the caller's policies don't allow the action; forbidden_origin: a cookie-authenticated write from an origin that isn't allowed; spend_limit_reached.
404
not_found: unknown, malformed, or in an organization the caller isn't in.
409
quota_exceeded (an allocation quota, with quota), idempotency_conflict, idempotency_in_progress (with Retry-After), organization_deletion_pending, operation_in_progress, or the endpoint's own 409 codes.
413
payload_too_large: the body is over the endpoint's limit (1 MiB unless it says otherwise).
429
too_many_requests, with Retry-After; or quota_exceeded (a rate, usage or concurrency quota, with quota), never with Retry-After.
500
internal_error: a bug; the details are in the logs, under the request ID.