Conflict
Another change landed first.
| Problem type | /problems/conflict |
|---|---|
| HTTP status | 409 |
| Emitted by | REST API (/v1) |
| Title values | Conflict |
| Trigger |
REST API (/v1):
concurrent-modification conflict
|
What happened
The engine detected a concurrent modification: two requests tried to change the same envelope at the same time and this one lost. The response is HTTP 409.
What it means
The other request’s change is in place; yours was not applied. This is rare outside parallel automation that edits one envelope from several workers.
What to do next
Re-read the envelope and retry the change against its current state. If you retried a POST with the same Idempotency-Key, see idempotency-in-flight instead.
Problem body
Every error the API returns is an RFC 9457 problem document with media type
application/problem+json. The type member is the
stable identifier to switch on; docs_url is this page.
{
"type": "/problems/conflict",
"title": "Conflict",
"status": 409,
"instance": "/v1/...",
"docs_url": "https://staging.signenvoy-docs-b4g.pages.dev/errors/conflict"
}