FruxonDocs
ApiAsync operations

Reports that the external work for an operation failed; the waiting run resumes with a failure outcome instead of blocking until the op's TTL.

Use this when the external system handling an async operation cannot deliver a result — the waiting agent run is re-queued with the supplied failure reason instead of waiting for the op's TTL to expire. Idempotent: replays against an already-terminal op return 204.

POST
/v1/tenants/{tenant}/asyncOperations/{asyncOperation}:fail

Authorization

Bearer
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

asyncOperation*string

The operation id (the callback token the tool issued).

Formatuuid
tenant*string

The tenant identifier

Request Body

The failure reason.

reason*string

A short, machine-readable reason surfaced to the waiting agent.

Length1 <= length
[key: string]?never

Response Body

curl -X POST "https://api.fruxon.com/v1/tenants/string/asyncOperations/497f6eca-6276-4993-bfeb-53cbbbba6f08:fail" \  -H "Content-Type: application/json" \  -d '{    "reason": "string"  }'
Empty
Empty
Empty
{
  "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
}