# Edit conflicts & duplicate warnings

> What the “Conflict Detected” toast and the merge dialogs mean, and how to resolve them.

_Collection: Troubleshooting & FAQ (troubleshooting) — Kepler Help Center. Canonical: https://keplercrm.com/support/articles/edit-conflicts/_

## "Conflict Detected — this record was updated by another user"

Two people edited the same record at the same moment, and your save arrived second. Kepler never silently overwrites the other person's change: your edit is rolled back and the table refreshes with the latest data. **Fix:** look at the refreshed value and re-apply your change if it's still right.

This protection covers all records — and shared work surfaces like CV import batches, where a reviewer colleague may be acting on the same drafts.

## "Another candidate already has this email"

Emails are unique per candidate (and per contact). If you set an email that another record already uses, Kepler opens a **merge dialog** so you can combine the two records deliberately — or warns you if a merge isn't possible. The same applies to company **domains**.

## Duplicate applicants and imports

  - Portal applications from the same email to the same posting within 24 hours are deduplicated silently — that's by design.

  - CV import drafts that match an existing candidate stop for **duplicate review**. Choose **Attach CV only**, **Update existing profile** or **Create as new candidate**. During the initial identity check, Kepler first offers **Parse full CV**; Update existing profile becomes available after detailed parsing.

  - If matching email or LinkedIn details prove the records are the same person, change or remove the duplicate identifier before creating a separate candidate.

> **NOTE:** If you believe a conflict fired in error — nobody else was editing — refresh the page and try again; a stale browser tab open since yesterday holds old versions of records and will conflict on first save.