«This record already exists.» or «Someone else changed…» (conflict, 409)

Symptom

When saving, «This record already exists.», «Someone else changed these settings. Refresh and try again.» or a similar "changed meanwhile" message appears. The API answers 409 conflict.

Cause

• Duplicate: a person with that email, a group with that name, a client with that identifier or a RADIUS address range already used by another client exists.
• Concurrency: another administrator saved the same object after you opened it; your version is no longer current (the server compares the expected revision).
• Idempotency: in an integration, the same Idempotency-Key was used with a different body.
• State: the operation does not fit the current state (for example cancelling a request already decided).

Fix

1. Refresh the view (or reopen the dialog) to read the current state.
2. Review what changed and repeat the change if it is still needed.
3. For a duplicate, choose another name or edit the existing object.
4. In an integration, use one idempotency key per operation and never reuse it with another body; read the resource's state.

When to escalate

If the conflict repeats with nobody else editing, contact support with the time, the view and the message.