One item of the automation's ledger.
Returns the item and ledger identifiers with withholding metadata in a protected view. The original view contains the item details shown in 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
Query Parameters
The requested content view. Joined originals require a Legacy workspace.
"AUTOMATIC""UNSPECIFIED" | "SAFE" | "MASKED" | "ORIGINAL" | "AUTOMATIC"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": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"ledgerId": "a2873d47-59a8-4daf-a325-cb2c04557dd7",
"itemKey": "string",
"label": "string",
"stageId": "string",
"status": "UNSPECIFIED",
"stageAttempts": 0,
"nextAttemptAt": 0,
"lastError": "string",
"admittedAt": 0,
"terminalAt": 0,
"lastExecutionRecordId": "65c1f865-d79b-4473-b445-cc7b98d5a651",
"batchRunId": "a74c20d6-643b-4445-9430-2d7b7d7f915e",
"batchId": "5579c111-9c50-47e2-af92-f16d52e63189",
"lastBatchId": "a6e65855-fa1b-4471-bfed-37018bee5f2d",
"data": null,
"admittedVia": "UNSPECIFIED",
"admittedBy": "string",
"admittedByExecutionRecordId": "42d7760a-367b-4a14-9325-cec12e179138",
"wakeAt": 0,
"waitingFor": "UNSPECIFIED",
"cost": 0,
"runs": 0,
"metadata": {
"contentVisibility": "UNSPECIFIED",
"redactedFields": [
"string"
],
"canReadOriginal": true,
"policyVersions": {
"property1": 0,
"property2": 0
},
"profile": "string"
}
}{
"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
}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.