One item's attempt history.
The append-only transition log: what happened to this item and why. The run tree answers a different question: why one attempt behaved as it did.
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 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.
Sort order.
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/transitions"{
"items": [
{
"id": "00000000-0000-0000-0000-000000000000",
"ledgerItemId": "00000000-0000-0000-0000-000000000000",
"stageId": "string",
"stageAttempt": 0,
"fromStatus": "READY",
"toStatus": "READY",
"cause": "string",
"detail": "string",
"executionRecordId": "00000000-0000-0000-0000-000000000000",
"producedKeys": [
"string"
],
"runExpected": false,
"runAvailable": false,
"agentId": "string",
"durationMs": 0,
"cost": 0,
"createdAt": 0
}
],
"nextPageToken": "string",
"totalCount": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Corrects a stuck or excluded work item's data, optionally re-driving it.
For a value an earlier stage recorded wrong — an ASK answer written as `SKIP` for a reply that said otherwise — which a re-drive alone would route on again. `set` maps paths to JSON values: a top-level key the item carries (or a declared path's root), or a dotted path a stage declares in `produces` or as an ASK stage's `answeredWhenPath`. A declared path takes only values its declaration allows — its type, null only when nullable, and for a form-asked answer only what the form accepts. Anything else is 400, naming what is settable. The reason is required. The correction is recorded as an `OPERATOR_SET_DATA` transition whose detail is the reason followed by each path's old and new value (credential-named paths masked); the status does not move. A correction that changes nothing records nothing. With `redrive: true` the item is also re-driven in the same transaction, exactly as `:redrive` does. Only DEAD, FAILED or IGNORED items: 409 otherwise, and 409 when the item changed between the read and the write.
Ends a work item's wait now, as if its due time had come.
For an item WAITING at a WAIT stage. The stage's due exit applies at once — the item continues to the next (or named) stage, or, under `onDue: FAIL` / `DEAD`, fails the window or gives up — and its history records `OPERATOR_WAKE` with the optional reason. Returns 409 when the item is not waiting at a WAIT stage, including when its wait ended between the read and the write.