Gets the result of a specific execution.
Returns the final output and metadata, including response content, token usage, and timing information.
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 execution record identifier.
The tenant identifier
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/agents/string/executionRecords/string/result"{
"agentExecutionRecordId": "00000000-0000-0000-0000-000000000000",
"agentId": "string",
"agentRevision": 0,
"parameters": {},
"result": {
"strValue": "string",
"jsonValue": null,
"fileLink": "string",
"flowControl": null
},
"createdAt": 0,
"tenantId": "00000000-0000-0000-0000-000000000000"
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Gets the raw OTLP spans archived for this execution.
Returns each span as we received it from the customer's tracer, no platform mapper applied. Used by the trace sidebar's "raw OTel" view and by external tooling driven off the source-of-truth (mapper validation, attribute audits). Empty `spans` array means the execution didn't go through OTLP ingest (native agent, or external run that emitted no spans).
Resumes a failed run, continuing the turn it died in.
A run that fails mid-turn keeps everything it had done: the suspend memo holds the tool calls it made up to its last suspension, and the per-call checkpoints hold everything it ran after that. This puts the run back on the queue so the worker replays those results — without re-invoking the tools — and carries on from the point that failed. It is the <b>same</b> execution record throughout, not a copy: the run is continuing, so its trace, cost and lineage stay whole. Refuses runs that parked before tool-result checkpointing existed. Their memo describes the turn as of the last suspension only, so anything they ran after it is invisible and would be re-invoked — twice-sent messages, twice-filed documents. Pass `force=true` only after checking the trace shows no tool calls after the last suspension. Also refuses a run whose schedule has fired again since it failed. The scheduler holds off while a run is alive, but a failed run frees its binding, so the next fire is correct and has already covered this ground — reviving the old run would put two runs of one schedule over the same work.