Run a schedule now
Starts one run of the schedule’s template now, whatever the schedule’s state and overlap policy, as POST /runs starts a saved agent’s run. The run carries the schedule’s id; the schedule’s occurrences are unchanged. While your organization is at its concurrency limit, the run is refused with 409.
Authorizations
Customer API key (axl_ prefix).
Path Parameters
The agent's id.
The schedule's id.
Response
Created
A run: of a saved agent, or of an ad hoc task.
Timestamp when the run record was created.
Run identifier.
agent: an agent works the task through a model. code: the agent's script runs.
agent, code Current lifecycle state of the run. paused: the run waits on a person; see input_request.
scheduled, queued, running, paused, completed, failed, cancelled Trigger identifies how the run was initiated.
manual, scheduled, api Timestamp of the last update to the run record.
User who initiated the run.
The agent the run is of; absent on an ad hoc run.
The agent's name, on the run lists; absent on an ad hoc run.
Timestamp when the run was cancelled.
Timestamp when the run finished.
Why the run failed.
What a paused run asks a person; answer it with :resume.
Until when an ended agent-mode run holds its phone: :sendMessage before then continues the run there; after it, start a new run.
Most the run's model steps may cost, in microdollars.
Most model steps the run may take.
The model the run's steps call, one of GET /models.
The network the run's code can reach: restricted reaches the phone only; internet adds the public internet.
restricted, internet The run's result, which satisfies its output_schema.
The JSON Schema the run's result must satisfy.
Longest the run waits paused for an answer, in seconds.
Phone executing the run.
An ad hoc run's own recording choice; absent takes the default (off), and a saved agent's run takes the agent's.
On a code run: whether the agent took over after the script failed, and the fix it proposed.
A short account of the run's result.
The agent's revision the run was pinned to when it was made.
Arbitrary metadata attached to the run.
The schedule that started the run, if one did.
Session associated with this run.
When the run was booked to start; absent for a run started on request.
How long the queued run may wait for a phone before auto-cancel.
Timestamp when the run began executing.
The run's live event stream (Server-Sent Events), with a short-lived read-only token. Server clients can send the API key header instead.
Whether the run completed without error.
The device the run drives.
An agent-mode run's task: the ad hoc task, or the agent's instructions.
An ad hoc run's own telemetry choice; absent takes the default (on), and a saved agent's run takes the agent's.
Longest the run may take, in seconds.
When the trace recording was deleted.
An agent-mode run's current turn, from 1.
Every turn of an agent-mode run, oldest first: the task, then each follow-up sent with :sendMessage.
What the run's model steps used, across its turns.
The run's inputs. Deleted once the finished run is older than the plan's run data retention window (30 days by default).
URL for the run recording video.