reservation_expired: A late confirm no longer fits after the hold expired
A reservation that is neither confirmed nor released is released by the scheduler once it is older than CORE_RESERVATION_TTL_SECONDS (default 3600, at least 60), and a reservation.expired webhook event is sent. A confirm that arrives later is still billed, under the same requestRef and exactly once, when every check a new meter passes still allows it. This code means one no longer did: for example the cap or the mandate, a revoke, a freeze or stop, the rate allowance, or a closed budget. The detail names that refusal. Nothing was billed, the refusal is recorded, and an alert is raised. A late confirm that only waits for a checkpoint answers checkpoint_pending instead.
What to do
- Confirm reservations soon after delivery; release them when delivery fails.
- If delivered work was refused this way, settle it under your own terms with the payer. The alert names the budget, stream, reservation and the refusal.
On the wire
HTTP 409, error type state_error.
With Dynamo-Error-Detail: 1:
{
"error": "state",
"detail": "…",
"errorDetail": {
"type": "state_error",
"code": "reservation_expired",
"message": "…",
"param": "requestRef",
"doc_url": "…/errors/reservation_expired.md",
"fix": "the hold was released by the reservation TTL and the late confirm no longer fits the cap or mandate; nothing was billed"
}
}
See all error codes.