Conflict
HTTP 409 ยท type https://qrbolt.com/developers/errors/conflict
What it means
The request conflicts with existing data: serials that are already registered (existingSerials lists them), a GTIN registered by another organization, a QR code changed since the version sent in If-Match (currentVersion gives the version now), overlapping time-based rules, job results requested before the job succeeded, two requests saving the same item SKU or GTIN at once, or a Barcode Manager rule given in code.
What to do
For serials, send onExisting: "skip" to ignore existing ones. For a version conflict, read the code again and retry with its new ETag. For job results, wait until the job has succeeded. For items, see code.
Reasons
Some of these problems carry reason (or code on a conflict) with one of these values. Branch on it as on type; the values never change.
NO_PREFIX- gtin "assign" was sent, but the organization has no GS1 prefix declared. An admin declares one in the dashboard.
PREFIX_FULL- gtin "assign" was sent, but the prefix has no free number left. Choose another declared prefix with prefix.
HAS_DIGITAL_LINK- change-number was refused because the item has a Digital Link, which encodes its GTIN. Archive its Digital Link codes first.
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