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.

curl -X POST "https://api.fruxon.com/v1/tenants/string/agents/string/executionRecords/string:resume"

{
  "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
}