Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One change · api

List Deployment Runs changedapi/beta/deployment_runs/list

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 191 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 191, old and new numbered
/
lines
from line 191
191191 
192192 - `agent: BetaManagedAgentsAgentReference`
193193 
194 A resolved agent reference with a concrete version.
194 Snapshot of the agent at fire time. Always fully resolved — deployments pin agent + version.
195195 
196196 - `type: "agent"`
197197 
from line 203
203203 
204204 - `created_at: string`
205205 
206 A timestamp in RFC 3339 format
206 Time this run record was persisted.
207207 
208208 format: date-time
209209 
from line 213
213213 
214214 - `error: BetaManagedAgentsEnvironmentArchivedRunError or BetaManagedAgentsAgentArchivedRunError or BetaManagedAgentsEnvironmentNotFoundRunError or 13 more or null`
215215 
216 Why the run failed to create a session. The type identifies the failure; message is human-readable detail.
216 Populated on creation failure. Null on success. Exactly one of `session_id` or `error` is non-null.
217217 
218218 - `BetaManagedAgentsEnvironmentArchivedRunError object`
219219 
from line 381
381381 
382382 - `trigger_context: BetaManagedAgentsTriggerContext`
383383 
384 Describes what triggered a deployment run, with trigger-specific metadata.
384 What triggered this run and trigger-specific metadata.
385385 
386386 - `BetaManagedAgentsScheduleTriggerContext object`
387387 
from line 391
391391 
392392 - `scheduled_at: string`
393393 
394 A timestamp in RFC 3339 format
394 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.
395395 
396396 format: date-time
397397 
Feedback