Update a schedule
Updates the configuration of an existing scheduled task.
Schedule Types:
- CRON (3): Use cronExpression to define a recurring schedule
- RunOnce (1): Requires startTime (must be in the future) - runs once at the specified date/time
- RunEvery (2): Uses runEveryCount and runEveryPeriod. Optional startTime for first run.
Authorizations
API Key authorization header. Example: "Authorization: ApiKey {your-api-key}"
OAuth 2.0 Bearer token. Example: "Authorization: Bearer {access-token}"
Path Parameters
The ID of the agent
The ID of the schedule to update
Body
The updated schedule configuration
Request model for updating an existing schedule
Name of the schedule (required)
Cron expression for the schedule (e.g., "0 9 * * 1,4" for Mon/Thu at 9am)
Local schedule expression (human readable)
Timezone for the schedule (e.g., "America/New_York")
Start date/time for the schedule in UTC.
- Required for RunOnce schedules (must be at least 1 minute in the future).
- Optional for RunEvery schedules (if provided, must be in the future; determines when the first run occurs).
- Not used for CRON schedules.
"2026-01-20T14:30:00Z"
JSON string of input parameters for scheduled runs
0, 1, 2, 3 Whether the schedule is enabled
Run every N periods (used with RunEveryPeriod)
Period unit for RunEveryCount (1=minutes, 2=hours, 3=days, 4=weeks, 5=months)
Parallelism level for the scheduled run
Max concurrency for parallel runs
Combined, Separated Proxy pool ID to use for scheduled runs
Server group ID for scheduled runs (optional). When specified, the schedule will run on servers in this group.
Fatal, Error, Warning, Info Text, TextAndHtml Whether to run exclusively (no concurrent runs)
Whether to wait on failure before retrying
Response
Returns the updated schedule
Represents a scheduled task for an agent in the External API
0, 1, 2, 3 Combined, Separated Fatal, Error, Warning, Info Text, TextAndHtml