Request already succeeded, response not kept
HTTP 409 · type https://qrbolt.com/developers/errors/idempotency-response-unavailable
What it means
An earlier request with the same key and body succeeded, but its response was not kept for replay: it was over 64 KB or past the daily volume of stored responses. (A file, such as an item barcode, never gets this: its key is released, and a retry renders the file again.) Nothing was done again. originalStatus gives the first status, and resource points at what was created when there is one.
What to do
Do not retry with a new key. Read the result instead, for example GET the resource, or list the serials you issued. To download a barcode again, send the request without an Idempotency-Key.
All error types
- 400 validation-error
- 400 bad-request
- 400 invalid-cursor
- 400 change-note-required
- 401 unauthorized
- 403 insufficient-scope
- 403 feature-not-enabled
- 403 gs1-not-enabled
- 403 forbidden
- 404 not-found
- 409 conflict
- 409 idempotency-in-progress
- 422 idempotency-key-reuse
- 409 idempotency-response-unavailable
- 402 active-code-limit-exceeded
- 415 unsupported-media-type
- 413 payload-too-large
- 429 rate-limited
- 500 internal-error
- 500 worker-lost
- 503 service-unavailable