409

Reservation expired

https://api.quotastack.io/errors/reservation-expired

The hold ran out before you closed it. QuotaStack gave the credits back, and charged nothing.

Why it happened

The job took longer than the ttl_seconds you set.
Nobody closed the hold, so a QuotaStack job swept it up.

How to fix it

Set a ttl_seconds longer than the job really needs.
Charge the customer with consumeEntitlement instead, now that you know the real cost.
Reserve again if the job has not started yet.

Example response 409

{
  "type": "https://api.quotastack.io/errors/reservation-expired",
  "title": "Reservation Expired",
  "status": 409,
  "detail": "Reservation has expired."
}

Which calls return this

POST /v1/reservations/{id}/commit

See also

Reservations

● raw markdown · reservation-expired.md ↗ — this is exactly what an agent fetches

Loading…