FruxonDocs
Agent NetworkTriggers

Returns every stuck or excluded work item in a selection to the queue.

The dead-letter queue's select-all. The selection is explicit ids or a filter (stage, status, ignore reason, admission window); it is resolved to a concrete set and that set's size must equal `confirmCount`, otherwise the call is refused with 409 and the real count — so a filter is only ever acted on as the items the operator saw. DEAD and FAILED items always qualify; an item a pass claimed in between is left alone and reported in the affected count. IGNORED items qualify only when the selection asks for them — `ignoreReason`, `status: IGNORED`, or explicit ids — so a re-drive filtered by stage alone still means the stuck items there. `status: IGNORED` on its own is refused with 400 and the count it would have moved: re-driving exclusions costs an agent run each, so the call has to name the reason that was revised or the ids. A named `ignoreReason` is matched whole against the reason as recorded, and is refused with 400 when the stage declares a set of reasons, this is not one of them, and no item on the ledger carries it either. When the selection is explicit ids, `skipped` names every id that was not acted on and why: it is not a work item at all, it belongs to another automation, or it was in a status this verb may not touch — carrying that status.

POST
/v1/tenants/{tenant}/triggers/{trigger}/ledger/items:redrive
AuthorizationBearer <token>

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

In: header

Path Parameters

trigger*string

The trigger identifier.

Formatuuid
tenant*string

The tenant identifier

The selection, an optional note, and the confirmed count.

selection*

What to re-drive. Required.

reason?string|null

Optional operator note recorded on every transition.

Lengthlength <= 4000
confirmCount*integer

How many items the caller expects the selection to match. The call is refused (409, with the real count) when it does not — the guard against acting on a set that changed between the read and the write.

Formatint32
[key: string]?never

Response Body

curl -X POST "https://api.fruxon.com/v1/tenants/string/triggers/497f6eca-6276-4993-bfeb-53cbbbba6f08/ledger/items:redrive" \  -H "Content-Type: application/json" \  -d '{    "selection": {},    "confirmCount": 0  }'
{
  "matched": 0,
  "affected": 0,
  "skipped": [
    {
      "itemId": "00000000-0000-0000-0000-000000000000",
      "itemKey": "string",
      "status": "READY",
      "reason": "NOT_FOUND"
    }
  ]
}
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
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
}