Update a schedule
Updates the configuration of an existing scheduled task.
Returns 400 if the Agent is archived — restore the Agent first before modifying its Schedules.
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.
Encrypted input parameters
Prefix a parameter name with ? to have its value encrypted at rest and hidden in
the Run log — for example "?apiKey" instead of "apiKey". The name you send decides
this. Sending a name without the ? prefix stores and logs the value in clear text,
even when the Agent defines that parameter as encrypted. Omitting a parameter
entirely leaves the Agent’s own definition in effect, encryption included.
If you send both "name" and "?name", the ?-prefixed entry is used and the plain
one is discarded. The request still succeeds.
A Schedule stores its input parameters, so a clear-text value is also returned in
clear text by GET /api/v1/agent/{agentId}/schedules to any caller with an API key
and read access to the Agent’s Space. Send ?name for anything sensitive.
Call GET /api/v1/agent/{agentId}/input-parameters to see which parameters an Agent
defines as encrypted.
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 = None; 1 = RunOnce; 2 = RunEvery; 3 = CRON
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
0 = Combined; 1 = Separated
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.
0 = Fatal; 1 = Error; 2 = Warning; 3 = Info
Fatal, Error, Warning, Info 0 = Text; 1 = TextAndHtml
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 = None; 1 = RunOnce; 2 = RunEvery; 3 = CRON
0, 1, 2, 3 0 = Combined; 1 = Separated
Combined, Separated 0 = Fatal; 1 = Error; 2 = Warning; 3 = Info
Fatal, Error, Warning, Info 0 = Text; 1 = TextAndHtml
Text, TextAndHtml