Why every update can be undone
Data Health only fills blanks or fixes formatting. Even so, a clean-up can touch thousands of records at once, and you may decide you preferred the old values. When an update runs, Vedain records the old and new value of every field it changes. You can use that log to put things back.
This applies to all three kinds of Data Health update:
- •Free clean-up fixes applied from the Leads, Contacts or Accounts tab.
- •AI enrichment runs (Company profile and Job-title intelligence), whether they were free under your allowance or a paid pack.
- •Inbox intelligence runs that update records from email replies.
Email typo fixes made in Email Verification have their own History list, which works the same way. See Quick check vs Mailbox verification.
Find the job history
History isn’t a separate tab. Each area of Data Health has its own History panel:
- •Leads, Contacts and Accounts tabs: the History panel sits below the clean-up rules and lists free fixes and AI enrichment runs for that module.
- •Inbox intelligence tab: the History panel at the bottom lists inbox runs.
Each row shows:
| You see | What it means |
|---|---|
| “5 fixes applied · 1,240 records” | A free clean-up job, with how many rules were applied and how many records changed. |
| “AI enrichment (Company profile + Job-title intelligence) · INR 499.00 · 206 records” | An AI enrichment run, with the pack fee charged (or INR 0.00 if it ran under your free allowance) and how many records it updated. |
| “Inbox intelligence · 58 records · INR 87.00 · 21 title, 14 phone …” | An inbox run, with a count of each kind of field it filled. |
| “Undo · 1,240 records” | An undo job, with how many values it restored. |
| “· undone” | This job has already been reversed. |
| “· running” | The job is still in progress. |
| “· failed” | The job stopped with an error. |
| “· interrupted (server restart) — undo reverts what it changed” | The job was cut off partway. See below. |
Under each description you see the date and time and the name of the person who ran it.
Undo a whole job
- Open the tab where the job ran, for example Leads, and scroll to History.
- Find the job and click Undo on the right.
- The row asks “Restore the earlier values?”. Click Undo to confirm, or Keep to leave everything as it is.
- The undo runs in the background with a progress bar. When it ends, a message says, for example, “Restored 1,240 values — The earlier values are back.”
- On the Leads, Contacts and Accounts tabs, Data Health then scans again so the rule cards match your data.
The original job is marked undone and its Undo button disappears. Each job can be undone once. Undo works through large jobs quickly: in our tests, hundreds of thousands of changed values were restored in a few minutes.
Undo never overwrites your later edits
Undo only restores a field if it still holds the value that job wrote. Say a clean-up changed a phone to +919876543210 and a colleague later typed a new number. Undo leaves the colleague’s number alone. That’s why the “Restored” count can be lower than the number of records the job changed.
Can I restore just one record?
Not at the moment. Undo works on a whole job, not on one record. To fix a single record, edit it directly. The change log keeps the old value of each field, and undoing the whole job restores every field that hasn’t been edited since.
If you only want some of a job’s changes, the safest route is to undo the job, scan again, and apply only the rules you want.
Interrupted jobs
Jobs run on Vedain’s servers, not in your browser, so closing the tab doesn’t stop them. If a server restarts while a job is running, the job stops partway and is reported straight away as interrupted (server restart) — undo reverts what it changed.
Some records will have been updated and some won’t. You have two choices:
- •Keep what was done and finish the rest. Scan again and apply the same fixes. Records that are already clean won’t show up again.
- •Reverse it. Click Undo on the interrupted row. Only the changes that were actually made are reverted.
If an AI or inbox run is interrupted, records it didn’t reach aren’t charged.
How long can I undo?
The field-level change log is kept for 180 days. Within that time you can undo any job that hasn’t already been undone. After 180 days those log entries expire. The job may still appear in History, but an undo would have nothing left to restore.
If you’re running a large clean-up before a migration or an audit, check the result within a few weeks rather than months.
What undo does not refund
Free clean-up rules cost nothing, so there’s nothing to refund. For paid runs:
- •AI enrichment (Company profile and Job-title intelligence): undo puts the earlier blanks back, but a paid pack fee isn’t refunded — the AI work was done when the run finished. A run that was free under your allowance has nothing to refund.
- •Inbox intelligence: undo puts the earlier values back, but the wallet charge isn’t refunded. The AI work was done and delivered when the run finished.
- •Records the AI couldn’t improve were never charged, so there’s nothing to recover for those.
- •Leads added or records marked as left from “People found in replies” are separate actions, not part of the run. Undoing an inbox run doesn’t delete a lead you added with Add as lead.
To limit what you spend in the first place, set a Spending cap before each paid run and check the estimate. See AI enrichment and Inbox intelligence: what they do and what they cost.
Who can undo
Undoing needs the same access as applying: edit access to Data Health and to the module involved (Leads, Contacts or Accounts; Leads and Contacts for inbox runs). If you don’t see Undo buttons, ask an Admin to check your role under Roles & permissions in Settings.
Related articles
- •Getting started with Data Health
- •AI enrichment and Inbox intelligence
- •Product overview: Data Health