Item counts per stage and status.
The stage funnel: how many items are in each stage and status, so a backlog, such as items sitting in one stage for days, is visible at a glance.
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
Query Parameters
The maximum number of items to return per page
int32int32Opaque pagination token returned by an external service. Pass it back unchanged rather than interpreting it as an offset.
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/triggers/497f6eca-6276-4993-bfeb-53cbbbba6f08/ledger/funnel"{
"items": [
{
"stageId": "string",
"status": "READY",
"count": 0,
"cost": 0,
"runs": 0,
"nextWakeAt": 0,
"overdue": 0
}
],
"nextPageToken": "string",
"totalCount": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Every reason this automation has excluded items for, with counts.
The options a filter-wide re-drive out of IGNORED is chosen from. An exclusion is a judgement a stage made under an instruction, so what an operator holds after revising that instruction is a reason rather than a list of items — and each count here is what `ignoreReason` resolves for that reason, which is what makes it confirmable. Distinct from the funnel, which stops at "1,204 IGNORED": a status is not something anyone can act on, and re-driving all of it would re-run every exclusion the shape has ever made. A reason with no recorded text comes back with a null `reason` — those items exist and cannot be selected by reason at all, and saying so is better than omitting them.
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.