Schedule a Task in an environment

POST 
/v1/schedules

One schedule per Task and environment. Schedules do not stack: the run is skipped if the Task already has an active or queued execution.

Request

Responses

201

created

401

INVALID_TOKEN / INVALID_AUDIENCE / INVALID_ISSUER / TOKEN_EXPIRED / TOKEN_REVOKED / MTLS_REQUIRED

403

INSUFFICIENT_SCOPE (see above) or FEATURE_NOT_ENABLED — the operation is not enabled for the organization (the same permission that enables the screen in the console); details: { permission }.

409

CONFLICT — the Task already has a schedule in the environment (details.schedule_id) / IDEMPOTENCY_KEY_REUSED

422

INVALID_CRON / VALIDATION_ERROR — Task or environment outside the organization

503

AS_UNAVAILABLE — token verification is unavailable (Authorization Server down or configuration missing). Try again (Retry-After).