Entry Revisions

Revisions provide an automatic, ordered record of entry answer snapshots and changes. There is no per-form switch; revision history is always available.

What you see

Open an entry and choose Revision History. Each card shows:

• Revision number
• Author type: user, admin, workflow, or system
• Admin email where it can be resolved
• Timestamp
• Optional edit reason
• Changed field paths with old and new values

Revision 1 represents the initial user submission. The current interface loads the latest 50 revisions and displays them newest first.

Main-entry admin edits

Selecting Edit Entry starts an edit session. Saving records pending changes and adds a revision with the optional reason. Cancelling discards the session; there is no separate restore action for a cancelled edit.

Metafield batching

Metafield values are edited continuously, so FormWork groups nearby changes into one revision instead of producing a card for every keystroke.

A batch is flushed after roughly one minute of inactivity, when the admin completes the metafield edit session, or after a maximum batching window of ten minutes. The resulting revision records the changes since the batch snapshot.

Metafield history belongs to the linked metafield entry and appears in its own Revision History view.

Workflow and system changes

When workflows or automatic FormWork actions change answers, the revision author type distinguishes them from respondent and admin work. Use Workflow Runs for automation details; the revision only describes the data change.

Snapshots and differences

Each revision stores a full answer snapshot and a change summary. The admin UI presents the changed paths but does not currently offer:

• Selecting two arbitrary revisions for side-by-side comparison
• A one-click restore/revert action
• Partial restore controls
• Revision deletion or enable/disable settings

To restore a historic value, review it in the card and make a new admin edit. That preserves the audit trail by creating another revision.

Practical use

• Ask admins to add a short reason for consequential corrections.
• Keep internal review state in metafields so its history is separate and readable.
• Interpret field paths using the entry’s stored form version.
• Export or use the API for audit processes that need more than the current 50-card interface.