Skip to content
Help Center
Troubleshooting & FAQ

Edit conflicts & duplicate warnings

How saving and Undo work, what “This record changed” and duplicate warnings mean, and how to resolve them.

How saving works

Edits show straight away: when you change a cell or a field, the new value appears at once and Kepler saves it in the background. If the save is refused, the old value comes back and Kepler tells you why, so nothing is lost silently. In a table, the next time you open that cell its editor starts from the value you tried to save, with the reason and Retry.

Changed your mind? In a table, press Cmd/Ctrl + Z to undo your last cell edit and Cmd/Ctrl + Shift + Z to redo it (not while you're typing in a field). Many other changes — deleting records, bulk pipeline moves, candidates added from CVs, accepting or declining an applicant — show a toast with Undo.

"This record changed" or "Someone else changed this field"

Someone else saved the same record after you opened it, and your save arrived second. Kepler never silently overwrites the other person's change:

  • In a table, the toast "This record changed" says your change wasn't saved, and the row is refreshed with the latest version. Look at the new value and make your change again if it's still right.
  • On a record page, the field shows the Saved value next to yours. Choose Apply my value to this version to save yours on top, or Discard to keep theirs.

Undo follows the same rule: if someone changed a field after your edit, undoing it is skipped ("Skipped — field changed") rather than overwriting their change.

"Duplicate email" or "Duplicate domain"

An email address belongs to one candidate (and one contact), and a domain to one company. If you set a value another record already uses, your change isn't saved and the toast offers Review & merge, so you can combine the two records deliberately. See Duplicates & data hygiene.

Duplicate applicants and CVs

  • Portal applications from the same email to the same posting within 24 hours are deduplicated silently — that's by design.
  • A CV in Add candidate that matches someone already in Kepler (same email, phone, LinkedIn or name) waits for you with a side-by-side comparison of This CV and the existing profile. Pick which value to keep on each line, then choose Merge into Name's profile. Or choose Attach CV only, New candidate (not offered when the email is the same) or Skip. While Kepler is still checking who the CV belongs to, the choices are Attach CV only, Different person and Skip.

If you believe a conflict fired in error — nobody else was editing — refresh the page and try again; a browser tab left open for a long time can hold old versions of records and will conflict on its first save.

Can't find what you need?

Send us the details and we will get back to you. Response times vary by request.

Contact support
Contact support