Version History
The version history shows who changed what, when on an entry — and lets you bring back earlier values.
In the interface, this area is called Changes.
Opening the history
Open an entry and switch to Changes.
For each change, you see:
| Item | Example |
|---|---|
| Who | {Name} edited this entry |
| When | Timestamp |
| What | Field name with Old and New |
Creation appears as {Name} created this entry.
Clicking the timestamp toggles between relative and absolute display: Click to switch between relative and absolute time format.
Load more changes loads older entries.
Who triggered a change
Not every change comes from a person:
| Display | Meaning |
|---|---|
| A name | A person made the edit |
| Form | The change came in via a form |
| System or Flow | A flow or an automatic process |
| Unknown user | The person can no longer be resolved |
The fastest way to the cause
If a value seemed to change "by itself," the history usually clears it up right away: if it says System or Flow, check this Grid's flows — one of them is probably reacting to a change and writing back.
Empty values appear as (empty), checkmarks as Yes and No. If a field has since been deleted, it shows Unknown field.
Restoring a value
Use Reset to this value to bring back an earlier value.
Resetting creates a new change
This does not delete the entry from the history. It creates a new change with the old value.
So the history isn't rewound. Instead, a further step is added that sets the old value again.
That's by design — the history stays complete. But: this new change is a change like any other and can start a flow with the Entry was changed trigger.
The confirmation dialog is called Create new change with old value.
Retention period
How far back the history goes depends on your plan. The app shows it, for example:
You have 1 week of revision history.
Depending on the plan, this shows 1 day, 1 week, or 4 weeks.
Older changes are gone for good
Once the retention period has passed, earlier values can no longer be viewed or restored.
For long-term traceability — for legal reasons, say — the version history isn't enough. In that case, deliberately log changes as data: an additional "Log" Grid that a flow writes to on every relevant change.
If nothing is available, No revision history available appears; while loading, Loading revision history….
What the history doesn't cover
Deleted entries can't be restored
The version history logs changes to the field values of an existing entry. A deleted entry is gone — the history doesn't bring it back.
So take a CSV export before larger deletion actions. → Deleting entries
Also not tracked: changes to structure — fields created, renamed, or deleted, changed views, forms, and flows.
Next
- Creating and editing entries
- Deleting entries
- CSV Export — backing up data