scheduled-deployments changedmanaged-agents/scheduled-deployments
Nearest release: v2.1.310, published 11 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
221
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits21to this page, all time
The whole hunk
from line 221, old and new numbered
/
from line 221
221221
222222The 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.
223223
224```text wrap
224```json
225225{
226226 "id": "depl_01xyz",
227227 "status": "active",
from line 574
574574
575575A 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.
576576
577```text
577```json
578578{
579579 "type": "deployment_run",
580580 "id": "drun_01abc124",
No line in this hunk matches that.