One item of the automation's ledger.
The same row `ledger/items` lists, for a caller holding a link to one item rather than a page of them — a run's trace pointing back at the item it processed, a deep link into the Work view.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The trigger identifier.
uuidThe ledger item identifier.
uuidThe tenant identifier
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/triggers/497f6eca-6276-4993-bfeb-53cbbbba6f08/ledger/items/497f6eca-6276-4993-bfeb-53cbbbba6f08"{
"id": "00000000-0000-0000-0000-000000000000",
"ledgerId": "00000000-0000-0000-0000-000000000000",
"itemKey": "string",
"label": "string",
"stageId": "string",
"status": "READY",
"stageAttempts": 0,
"nextAttemptAt": 0,
"lastError": "string",
"admittedAt": 0,
"terminalAt": 0,
"lastExecutionRecordId": "00000000-0000-0000-0000-000000000000",
"batchRunId": "00000000-0000-0000-0000-000000000000",
"batchId": "00000000-0000-0000-0000-000000000000",
"lastBatchId": "00000000-0000-0000-0000-000000000000",
"data": null,
"cost": 0,
"runs": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Deliberately excludes every work item in a selection, with one reason.
"Drain this stage" is this verb with a stage filter. Same selection and confirmation rules as the re-drive; only READY, FAILED and DEAD items qualify, never one a pass holds. An explicit-id selection gets the same `skipped` list, naming what was left alone and why.
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.