One item's durable side effects, and how sure the platform is about each.
What this item has done to the outside world. The status that matters is `UNKNOWN`: a previous attempt left the record open, so the platform refuses to repeat the effect and the item cannot pass its stage — re-driving it hits the same refusal. Those rows carry `canSettle`, and `:settle` is how a person who has gone and looked ends the doubt. `docs/design/item-ledger.md §6.4`.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The automation.
uuidThe ledger item 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.
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/effects"{
"items": [
{
"id": "00000000-0000-0000-0000-000000000000",
"ledgerItemId": "00000000-0000-0000-0000-000000000000",
"effectKey": "string",
"status": "PENDING",
"externalRef": "string",
"detail": "string",
"attempts": 0,
"executionRecordId": "00000000-0000-0000-0000-000000000000",
"createdAt": 0,
"modifiedAt": 0,
"resolvedAt": 0,
"canSettle": false
}
],
"nextPageToken": "string",
"totalCount": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}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.
Records what a person found about an effect the platform could not resolve.
The way out of an UNKNOWN effect, which otherwise parks its item permanently. The operator checks the external system and answers the question the platform could not: `LANDED` closes the effect so a later attempt skips the call, `DID_NOT_LAND` reopens it so the next attempt performs it. Answer it wrong in the second direction and the effect is duplicated — which is the failure the durable-effect record exists to prevent — so the reason is required, and only an `UNKNOWN` effect may be settled at all. Returns 409 for any other status: a PENDING row may have a worker mid-call against it. Settling does not re-drive the item; that stays a separate decision.