Skip to main content
HTTP 409: Earlier write’s outcome unknown. Retry the request unless the body says retryable: false: wait for Retry-After when the response has one. Errors never cost API credits. The body carries the earlier write’s change_id. While Alura is still checking whether that write landed, the answer is retryable with Retry-After. Once Alura has stopped checking (24 hours after it was sent, its outcome still unknown), a repeat of the same write gets the same answer with retryable: false: check the write on Etsy instead. For a create, the block lasts up to 24 hours after Alura stopped checking, and the answer names the time; allow_duplicate: true with a new request key creates it anyway, and for a listing, a shipping or processing profile, a section or a return policy a repeat is sent once Alura sees that the object the earlier write made was deleted. For a shipment or a review response, which Alura never adds twice, this answer does not expire. A retry under the earlier write’s own request key answers its change instead. What to do: The same write was sent earlier and Alura does not know whether it landed on Etsy; nothing was sent again. Check the change at change_id before writing again.
Response
The response is application/problem+json (RFC 9457) and has a Request-Id header with the same request_id. See all errors.