Run Deployment Now changedapi/beta/deployments/run
Nearest release: v2.1.283, published 3 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+5added
Lines−5removed
From line
141
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits10to this page, all time
The whole hunk
from line 141, old and new numbered
/
from line 141
141141
142142 - `agent: BetaManagedAgentsAgentReference`
143143
144 A resolved agent reference with a concrete version.
144 Snapshot of the agent at fire time. Always fully resolved — deployments pin agent + version.
145145
146146 - `type: "agent"`
147147
from line 153
153153
154154 - `created_at: string`
155155
156 A timestamp in RFC 3339 format
156 Time this run record was persisted.
157157
158158 format: date-time
159159
from line 163
163163
164164 - `error: BetaManagedAgentsEnvironmentArchivedRunError or BetaManagedAgentsAgentArchivedRunError or BetaManagedAgentsEnvironmentNotFoundRunError or 13 more or null`
165165
166 Why the run failed to create a session. The type identifies the failure; message is human-readable detail.
166 Populated on creation failure. Null on success. Exactly one of `session_id` or `error` is non-null.
167167
168168 - `BetaManagedAgentsEnvironmentArchivedRunError object`
169169
from line 331
331331
332332 - `trigger_context: BetaManagedAgentsTriggerContext`
333333
334 Describes what triggered a deployment run, with trigger-specific metadata.
334 What triggered this run and trigger-specific metadata.
335335
336336 - `BetaManagedAgentsScheduleTriggerContext object`
337337
from line 341
341341
342342 - `scheduled_at: string`
343343
344 A timestamp in RFC 3339 format
344 The UTC instant at which the cron expression matched in the configured timezone, before jitter is applied. At most one run is recorded per (`deployment_id`, `scheduled_at`) pair.
345345
346346 format: date-time
347347
No line in this hunk matches that.