Cancels the active provider turn of a live session and keeps its owned process running; it is the non-terminal control, /stop remains the terminal one, and the optional body decides which control plane answers — absent, it is the legacy interrupt of a non-work run; with a positive work_lease_fence, it is the fenced control this work-bound run's input and stop already use.
const url = 'https://example.com/v1/m/sessions/runs/example/interrupt';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"work_lease_fence":1}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/v1/m/sessions/runs/example/interrupt \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "work_lease_fence": 1 }'Cancels the active provider turn of a live session and keeps its owned process running; it is the non-terminal control, /stop remains the terminal one, and the optional body decides which control plane answers — absent, it is the legacy interrupt of a non-work run; with a positive work_lease_fence, it is the fenced control this work-bound run’s input and stop already use.
Authorizations
Section titled “ Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “ Path Parameters ”Path parameter ref.
Header Parameters
Section titled “ Header Parameters ”Target tenant id; required when the principal can act in more than one tenant.
Request Body
Section titled “ Request Body ”Optional fenced turn interruption. An empty body preserves legacy non-work run behavior; a positive work_lease_fence selects the same fenced WorkItem control plane this run’s input and stop use. It cancels the active provider turn only: the owned process, its conversation and the run stay usable for the next input, and it never falls back to stop.
object
Example generated
{ "work_lease_fence": 1}Responses
Section titled “ Responses ”The run resource after the control was applied
object
The operated session’s stable reference.
The run’s derived lifecycle state after the control.
Example generated
{ "run_ref": "example", "state": "example"}Bad request
object
Example generated
{}Unauthenticated
object
Example generated
{}Forbidden
object
Example generated
{}Not found
object
Example generated
{}Conflict / setup required
object
Example generated
{}Rate limited
object
Example generated
{}The outcome is UNKNOWN: required authority, evidence or store could not be observed, and any external effect may or may not have crossed
object
The durable outcome name, e.g. work_input_ambiguous or evidence_unavailable.
object
Present when the refusal names the field or evidence it could not resolve.
The uncertain verdict: the outcome could not be observed.
Example
{ "verdict": "NO_HE_PODIDO_MIRAR"}