resource_locked
Another operation holds the resource until it finishes: concurrent writes on the same object are serialised instead of interleaved. On `POST /v1/companies/{company}/invoices` with `external_id`, another request with the SAME `external_id` is still in progress and had not finished after waiting 20 seconds.
| Code | Type | HTTP | Category |
|---|---|---|---|
resource_locked | conflict_error | 409 | Request |
Cause
Another operation holds the resource until it finishes: concurrent writes on the same object are serialised instead of interleaved. On POST /v1/companies/{company}/invoices with external_id, another request with the SAME external_id is still in progress and had not finished after waiting 20 seconds.
What to do
Retry after a short back-off and reuse the same Idempotency-Key, so the retry cannot duplicate the write. In the unattended checkout the request that waited wrote nothing: resend the same request (same external_id) and it will return the invoice already issued.