409 Conflict
The request conflicts with the current state of the target resource, and the client may be able to resolve the conflict and resubmit.
4xx · Client error
Typical causes
Two edits racing on the same record, creating something whose name already exists, or an operation that is not allowed in the resource's current state.
On Bex
From the Bex API, resolve the name or state conflict before retrying — for example, a Blueprint sync answers 409 with BLUEPRINT_SYNC_BUSY while another sync runs.
Defined in RFC 9110, §15.5.10