Resume a schedule
Turn a paused schedule back on. It picks up its cadence from now.
STATE_PAUSED back to STATE_ACTIVE. It computes the next fire from the current time forward; it does not backfill the runs that a pause skipped.
Only a paused schedule resumes
Resume works onSTATE_PAUSED. Resuming an archived schedule is a 400, archiving is terminal, so create a new schedule instead. Resuming an already-active schedule is a safe no-op.
Related
Pause a schedule
List schedules
nextFireAt after resuming.Create a schedule
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Workspace ID.
"workspace_01HXKD2E5NQM3T9AYWCF133E3Q"
Agent ID. Accepts the canonical agent_… form or the external_id:<value> form.
"agent_01HXKD2E5NQM3T9AYWCFMGWT9Y"
Schedule ID. Accepts the canonical as_… form or the external_id:<value> form.
"as_01HXKD2E5NQM3T9AYWCFMZZZBD"
Body
Resume agent schedule request.
Response
OK
AgentSchedule resource — a recurring trigger attached to an agent that creates objectives on its cadence.
Standard metadata for persistent, named resources (e.g., agents, tools, prompts)
AgentScheduleSpec is the user-provided configuration for a schedule.
The current lifecycle state of the schedule. Output only. Schedules are created STATE_ACTIVE; use the :pause, :resume, and :archive actions to transition between states.
STATE_UNSPECIFIED, STATE_ACTIVE, STATE_PAUSED, STATE_ARCHIVED AgentScheduleInfo provides read-only runtime data about a schedule.