Shows what is gathering at the automation's batch stages.
Items at a stage that processes in batches wait, unclaimed, until their group closes: when it is full, when its oldest item has waited the stage's window, or when nothing upstream can still feed it. For each batch stage this returns its rules, its runs in flight, and each group with its size, where it stands and — while it is still gathering — when its window closes it. A fire with `closeGathering` closes them all now.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The trigger identifier.
uuidThe tenant identifier
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/triggers/497f6eca-6276-4993-bfeb-53cbbbba6f08/ledger/gathering"{
"stages": [
{
"stageId": "string",
"groupBy": "string",
"maxMembers": 0,
"gatherMinutes": 0,
"running": 0,
"maxRunning": 0,
"upstreamDrained": false,
"heldUntil": 0,
"groupCount": 0,
"groups": []
}
]
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Item counts per stage and status.
The stage funnel — design §6.5's accounting query as an endpoint, so "15 items sat in awaiting_destination for 3 days" is visible at a glance instead of being a memory blob someone has to know to read.
Lists the automation's work items.
The Work view's item grid. Filter by stage and status; the UI defaults to DEAD + FAILED first, because the dead-letter queue is the reason this view exists. `ignoreReason` narrows to the items one exclusion reason set aside, matched whole and case-sensitively, and is the filter that makes `totalCount` the number `items:redrive` will confirm for the same selection. Without it the client could see "1,204 IGNORED" and the 29 rows its current page happens to hold, and nothing in between.