exposure: The unsettled exposure limit is reached
The service node's protections refuse more work for now. One of these holds:
- the service node's unsettled work plus this request would go over its unsettled-exposure limit;
- for a reservation, the service node already has as many held reservations as its concurrent unpaid-work limit allows;
- the budget's remaining headroom is below the last degradation band (by default under a tenth of the budget is left);
- the budget is in the throttled band (by default between a quarter and a half left) and the request is larger than the per-request maximum.
Inside the checkpoint band, a stream with unsettled work of its own is refused until the next checkpoint. Without Dynamo-Error-Detail: 1 that refusal is this same body (reason exposure) with a Retry-After header; with the header its detail code is checkpoint_pending.
What to do
- Let the next checkpoint settle the outstanding work (the scheduler runs it), then retry.
- In the throttled band, send smaller requests; when the budget is nearly spent, open a new budget.
- Retrying with the same
requestRefis safe: it is billed at most once.
On the wire
HTTP 409, error type halted.
A client that does not send Dynamo-Error-Detail: 1 gets the same body without errorDetail, except on the payment authorization and receipt routes and the test-fixture run route (POST /owner/v1/test-fixtures/streams/{id}/run), which send it to every client. The detailed body:
{
"error": "halted",
"reason": "exposure",
"streamId": "stm_…",
"detail": "…",
"errorDetail": {
"type": "halted",
"code": "exposure",
"message": "…",
"param": null,
"doc_url": "…/errors/exposure.md",
"fix": "the service node's unsettled exposure limit is reached; checkpoint (settle) and retry"
}
}
See all error codes.