scheduled-deployments changedmanaged-agents/scheduled-deployments
Nearest release: v2.1.308, published 2 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+2added
Lines−2removed
From line
224
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits18to this page, all time
The whole hunk
from line 224, old and new numbered
/
from line 224
224224
225225The response includes a deployment object with a populated `schedule.upcoming_runs_at` with the next upcoming fire times, to confirm your schedule was set correctly.
226226
227```json
227```text wrap
228228{
229229 "id": "depl_01xyz",
230230 "status": "active",
from line 578
578578
579579A failed run includes an `error` with a `type` describing why session creation was rejected (for example, `environment_archived_error`, `agent_archived_error`, or `session_rate_limited_error`). See the [List Deployment Runs](https://platform.claude.com/docs/en/api/beta/deployment_runs/list) reference for all filter parameters and the response schema.
580580
581```json
581```text
582582{
583583 "type": "deployment_run",
584584 "id": "drun_01abc124",
No line in this hunk matches that.