Yesterday, I changed the name in the primary field of a record for clarity. Today, when I looked at the view the record was in, I saw the name had been reverted back to what it was before I edited it yesterday. According to the revision history, 22 hours ago, I made the change (ex. International House of Pancakes to IHOP), and an hour ago I undid the change (ex. IHOP to International House of Pancakes).
While I had two tabs open, I had not been in either of them today until the time I noticed the change, and certainly not an hour ago. Neither had the record open to possibly mess with the name change reverting. This is the only computer I have the account signed into. I know I didn’t actively change it back.
Does anyone have any idea what happened here?
I feel like this has happened to my team a handful of times, where (usually the primary record) randomly changes back, with the person who was listed as having made the change swearing they didn’t do it.
Best answer by Leo Luo
A tab sitting in the background will not randomly send updates, but there are 2 triggers could cause this exact rollback:
Dirty Input Blur:
If the primary cell was left in an active editing state (cursor blinking inside the cell) in a tab before you switched away, the tab held that stale text in its local input buffer. When you clicked back into the tab after some time, clicking anywhere outside that cell triggered an onBlur event. It committed its uncleaned local buffer to the server as a new edit, which Airtable logs as an Undo.
Extension Autofill on Tab Wake:
If your browser discarded the background tab to save memory, reactivating the tab rehydrates the DOM. Form autofill extensions (such as password managers) can misidentify the field and inject previously cached values into the reloaded inputs.
Closing background tabs rather than leaving uncommitted cells open across tab sleep cycles will prevent this buffer collision.
One thing I’d check is whether any automations, scripts, or external integrations are updating that primary field. It would also be worth checking the revision history alongside any automation run history around the time the value reverted. Has this happened only with primary fields, or have you noticed it with other fields too?
@Mercerntino has a good idea there, although Automations will clearly show the change as an automation, it doesn’t connect it to a person.
@KimF Another thing is if you use CTRL+Z often, this can definitely be the cause. Especially if you have two screens open, let’s say you meant to do CTRL+Z on your left screen on word or somehting but were clicked onto your Airtable screen by mistake, you’ll undo that change even if it was a long time ago, as long as you have not left the view. I’ve had this happen to me as I use CTRL+Z all the time.
Now if you closed the Airtable/view since then that should not be the case and I have no other suggestions for ya! :)
One thing I’d check is whether any automations, scripts, or external integrations are updating that primary field. It would also be worth checking the revision history alongside any automation run history around the time the value reverted. Has this happened only with primary fields, or have you noticed it with other fields too?
The only time I’ve noticed it was with the primary field. We use automations, but none of them would alter the name. They’re mostly used to take existing data in Airtable and send it to other platforms (ex. Alerting a Slack channel to a status update, sending an email to someone in the record’s user field, etc.), rather than the other way around.
Instances in the past where I've seen it happen before with another colleague were in a table that doesn’t have any automations at all.
@Mercerntino has a good idea there, although Automations will clearly show the change as an automation, it doesn’t connect it to a person.
@KimF Another thing is if you use CTRL+Z often, this can definitely be the cause. Especially if you have two screens open, let’s say you meant to do CTRL+Z on your left screen on word or somehting but were clicked onto your Airtable screen by mistake, you’ll undo that change even if it was a long time ago, as long as you have not left the view. I’ve had this happen to me as I use CTRL+Z all the time.
Now if you closed the Airtable/view since then that should not be the case and I have no other suggestions for ya! :)
It’s a possibility, but in that instance would it trigger 20 hours later? I’m sincerely asking, because I am guilty of a good CTRL+Z screw-up every now and then, but in this instance I hadn’t used Airtable at all that day until I noticed the change, let alone the hour before that it claimed I had made the change.
Again, sincere question, would CTRL+Z affect changes made by other people? In a colleagues case, I had changed the name of something from ZYX to XYZ, and the revision history said they changed it back, and when I asked them about it, they swore they weren’t in the record. While I am fully aware people lie and accidentally mess with things they shouldn’t all the time, I will say in this instance, I do have good reason to believe them when they said it.
@Mercerntino has a good idea there, although Automations will clearly show the change as an automation, it doesn’t connect it to a person.
@KimF Another thing is if you use CTRL+Z often, this can definitely be the cause. Especially if you have two screens open, let’s say you meant to do CTRL+Z on your left screen on word or somehting but were clicked onto your Airtable screen by mistake, you’ll undo that change even if it was a long time ago, as long as you have not left the view. I’ve had this happen to me as I use CTRL+Z all the time.
Now if you closed the Airtable/view since then that should not be the case and I have no other suggestions for ya! :)
It’s a possibility, but in that instance would it trigger 20 hours later? I’m sincerely asking, because I am guilty of a good CTRL+Z screw-up every now and then, but in this instance I hadn’t used Airtable at all that day until I noticed the change, let alone the hour before that it claimed I had made the change.
Again, sincere question, would CTRL+Z affect changes made by other people? In a colleagues case, I had changed the name of something from ZYX to XYZ, and the revision history said they changed it back, and when I asked them about it, they swore they weren’t in the record. While I am fully aware people lie and accidentally mess with things they shouldn’t all the time, I will say in this instance, I do have good reason to believe them when they said it.
Hi Kim,
To your two questions:
Can Ctrl+Z undo something 20 hours later? Yes, if the tab stayed open. Undo history lives in the browser tab, so one of your two open tabs could have undone the edit when it got a stray Ctrl+Z, and it would show as you.
Can it undo someone else's change? It shouldn't. Undo only reverses edits made in that same tab. For your colleague's case, check revision history for other records changed at the same minute. If there are some, it was likely a paste over old data. If not, they probably edited from a tab opened before your change.
Cherry, Founder at Claribase If you are interested in booking a call, please book me here: https://calendly.com/cherryyang/initial-consultation
A tab sitting in the background will not randomly send updates, but there are 2 triggers could cause this exact rollback:
Dirty Input Blur:
If the primary cell was left in an active editing state (cursor blinking inside the cell) in a tab before you switched away, the tab held that stale text in its local input buffer. When you clicked back into the tab after some time, clicking anywhere outside that cell triggered an onBlur event. It committed its uncleaned local buffer to the server as a new edit, which Airtable logs as an Undo.
Extension Autofill on Tab Wake:
If your browser discarded the background tab to save memory, reactivating the tab rehydrates the DOM. Form autofill extensions (such as password managers) can misidentify the field and inject previously cached values into the reloaded inputs.
Closing background tabs rather than leaving uncommitted cells open across tab sleep cycles will prevent this buffer collision.
Adding to Cherry: revision history credits whoever's session made the change, so a Ctrl+Z in a tab someone left open shows under their name, even a day later. Check if other records changed in that same minute. Free only keeps 2 weeks of history, so screenshot it now if you need it.