What each pass admitted, dispatched, finished and spent.
Ledger passes, newest first, with transition counts and attributed execution cost. Cost may increase after firedAt while the pass's executions finish; an immediate read can therefore report less than the final cost.
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/passes"{
"items": [
{
"id": "00000000-0000-0000-0000-000000000000",
"firedAt": 0,
"source": "SCHEDULE",
"outcome": "FIRED",
"detail": "string",
"admitted": 0,
"dispatched": 0,
"completed": 0,
"runs": 0,
"cost": 0,
"betweenPasses": {
"firstClaimedAt": 0,
"lastClaimedAt": 0,
"dispatched": 0,
"completed": 0,
"runs": 0,
"cost": 0,
"causes": []
}
}
],
"nextPageToken": "string",
"totalCount": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}What happened to the automation's items, bucketed over time.
Per bucket: items admitted, and transitions to DONE (`finished`), IGNORED (`setAside`) and DEAD (`dead`). These are events, not item states: an item re-driven after it finished and finished again counts in both buckets, and an item an operator set aside by hand counts as set aside. Admitted is not part of the other three, because an item usually finishes in a later bucket than it arrived in. Counted from the transition log, which is never purged, so the whole window is counted unless it is longer than 400 days; then only its last 400 days are, and `countedFromMs` says where counting began. Buckets with nothing in them are omitted.
Starts the ledger over.
Destructive. Cancels every open batch (settling its human task and closing its conversation), deletes every item, effect and dedupe key, and moves the cursor to an empty position under a new version so an in-flight pass loses its write. The items' transitions are kept as history. Refused with 409 when `confirmItems` is not the ledger's current item count, or while a running pass holds a claim. The effects' external targets are not touched — the next pass performs them again.