idempotency_conflict
The same Idempotency-Key was used for a different request within 24 hours.
Common causes
- reusing a key for a different request body
What to do
- Use a new UUID for every logical request.
| Retry? | No, the result will be the same unless the request changes. |
|---|---|
| Billing | 0 units. |
type | https://maticna.si/docs/errors/idempotency_conflict |
Example response
HTTP/1.1 409Content-Type: application/problem+jsonX-Request-Id: req_01JB2Q8X6S7T{ "type": "https://maticna.si/docs/errors/idempotency_conflict", "title": "Idempotency key reused with a different request", "status": 409, "detail": "The same Idempotency-Key was used for a different request within 24 hours.", "instance": "/v1/entities/12345679", "code": "idempotency_conflict", "request_id": "req_01JB2Q8X6S7T"}Other errors with status 409
cursor_expired· Cursor expired
Source: FURS · unofficial source, not an official extract · Terms · Privacy · maticna.si