Deliberately excludes a work item, with a reason.
For genuine business exclusions — "group policy, insured is not an agency client" — which must stay visible and distinct from a failure. The reason is required: an exclusion without one is indistinguishable from a bug six months later, and the recorded reason is the only thing separating IGNORED from DEAD.
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
The required reason.
Why this item is being excluded. Required.
1 <= length <= 4000Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/triggers/497f6eca-6276-4993-bfeb-53cbbbba6f08/ledger/items/497f6eca-6276-4993-bfeb-53cbbbba6f08:ignore" \ -H "Content-Type: application/json" \ -d '{ "reason": "string" }'{
"id": "00000000-0000-0000-0000-000000000000",
"ledgerId": "00000000-0000-0000-0000-000000000000",
"itemKey": "string",
"label": "string",
"stageId": "string",
"status": "READY",
"stageAttempts": 0,
"nextAttemptAt": 0,
"lastError": "string",
"admittedAt": 0,
"terminalAt": 0,
"lastExecutionRecordId": "00000000-0000-0000-0000-000000000000",
"data": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}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.
Returns a stuck work item to the queue.
The dead-letter escape hatch. A DEAD item has exhausted its attempts and a FAILED one is waiting out a backoff; re-driving either resets its attempt count so it gets a full budget again rather than dying on the next failure, and hastens a sweep so it is picked up now instead of at the next scheduled window. Returns 409 when the item is not in a state an operator may act on — notably while a pass still holds its claim.