type URI on every conflict problem body: https://docs.get-exo.com/errors/conflict.
HTTP status: 409 Conflict.
Why it happens
This is the default 409 code. It is raised directly whenPUT /v1/subjects/{subject_id} is handed the key owner’s own user id, which is already the default identity every unselected call acts as.
Most 409s in the API are named: job_not_cancelable, export_not_ready, webhook_limit_reached, purge_impact_changed, idempotency_in_flight, connector_not_syncable, sandbox_subject_conflict and subject_mapping_invalid.
How to fix it
- Choose a different subject id. Use the id your own product has for that end user rather than an Exo internal id.
Related
subject_mapping_invalidsandbox_subject_conflict- Errors for the envelope and the full catalogue