Skip to main content

Escalations

The escalations resource covers the full lifecycle. Creating escalations uses a workspace apiKey; the read and reviewer methods act on behalf of a user, so use a client built with token or getToken (see Client).

escalate

Convenience wrapper that creates an escalation under a policy. The policy key is the first argument; everything else is the decision content.
escalate returns as soon as TryAgent creates the escalation — it does not wait for a reviewer. Required fields are agentId, runId, subject, question, evidence, and choices. Optional fields include responseFields, severity, resume, and metadata.

escalations.create

The same call as escalate, with policy included in the input object. Use it when you already have a fully assembled CreateEscalationInput.

escalations.list

Returns escalations for the workspace, optionally filtered by status. Resolves to an Escalation[] (the SDK unwraps the API envelope).
status accepts open, acknowledged, decided, resolved, breached, or canceled. Omit it to list all.

escalations.get

Fetch a single escalation by id, including its current status, decision, and learned recommendation when present.

escalations.acknowledge

Mark an open escalation as being worked on. Only open escalations can be acknowledged.

escalations.decide

Record a reviewer decision and resolve the escalation. choice must match one of the escalation’s choice ids. Include response when the escalation defined responseFields.
Deciding triggers the signed resume callback to your resume.url. Verify it with webhooks.constructEvent.

escalations.cancel

Cancel an escalation without recording a choice — for example, when the underlying run is abandoned.
Both decide and cancel reject escalations already in a terminal state (decided, resolved, breached, canceled).