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.
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 cursor token from an external system (e.g. RAG API). When set, M:Fruxon.Common.Collections.PageToken.AsString returns this value directly instead of encoding Fruxon.Common.Collections.PageToken.Skip.
Optional stage filter, matching the selection's own.
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/triggers/497f6eca-6276-4993-bfeb-53cbbbba6f08/ledger/exclusions"{
"items": [
{
"reason": "string",
"count": 0
}
],
"nextPageToken": "string",
"totalCount": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Moves the cursor — where the next scan starts.
A compare-and-swap on the version the operator read from `GET …/cursor`: a pass that advanced it in between wins and the reset is refused with 409. Moving the cursor never re-runs admitted work (admission collides on the item key); it decides where the next scan begins. Null starts from the door's own horizon.
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.