conflict

HTTP 409. Conflict.

When you see it

An Idempotency-Key was reused with a different body, or a request with that key is still in flight. Also: POST /v1/keys when the account already has 25 active access keys, and POST /v1/inbox/{id}/move on an image or file capture that is still pending (its bytes are only on the device that shared it), or on a capture that was already filed or archived (filing it again would make a duplicate).

What to do

Use a fresh key for a new request, and the SAME key with the SAME body when retrying. For the key limit, revoke one first. For a pending capture, wait for its inbox.updated event (or poll the row until pending is false) and send the same move again. For a capture that was already filed, read it: movedTodoId, movedNoteId or attachmentId names what it became.

The body

type is https://devs.inittasks.com/errors/conflict. instance is the path that failed, here /v1/todos. For the full RFC 9457 shape, the request_id field and the retry rules, see errors and retries.