Terminally cancels a parked run, ending the execution.
The stronger counterpart to `:cancelWait`. Where cancelling the wait resolves the consult and <b>resumes</b> the run (so the agent can re-issue the same consult and re-park), this kills the run: every op the task is parked on is torn down, the task is flipped to a terminal state that never resumes, and the execution record is marked `Cancelled`. Use it when the run is stuck in a re-consult loop and skipping the single consult would not end it. Only a run parked `WAITING_FOR_ASYNC` can be cancelled.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The unique identifier of the agent.
The parked execution record to cancel.
The tenant identifier
Optional cancellation reason.
Optional free-text reason recorded on the cancelled operation(s) and in the audit log.
Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/agents/string/executionRecords/string:cancelRun" \ -H "Content-Type: application/json" \ -d '{}'{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Adds an execution to one or more evaluation datasets as a sample
Snapshots the execution's inputs and outputs into each target dataset as an `EvaluationSample`, tagged with the supplied free-form tags. Use this to curate real-traffic examples into golden sets, regression suites, or labeled pools that feed evaluation runs. Re-adding the same execution to a dataset creates a new sample row rather than upserting, so callers that want at-most-once semantics should dedupe via `GET .../executionRecords/{executionRecord}/samples` first.
Cancels the consult a parked run is waiting on, resuming the run.
When a run is parked `WAITING_FOR_ASYNC` on a `consult_participant` to a human who hasn't answered, this lets an operator end the wait now instead of waiting out the consult's 24h TTL. The consult's proposal/topic is withdrawn and the run resumes with the same `no_answer` outcome it would get on a timeout — so cancelling introduces no new run behavior. Approvals are cancelled through their own `pendingApprovals/{id}:cancel` endpoint, not here.