Managing Entries

An entry is one respondent session. Open a form from its project to work with entries, saved views, import/export jobs, and form-level files.

Entry status

Workflow runs have their own started, completed, or failed status. They do not turn an entry into a processing/error status.

Entry list

The Entries tab displays the active saved view, 20 rows at a time. A view controls both the filter and visible columns. You can:

• Switch, create, edit, delete, or set a default view
• Select individual or all visible rows
• Delete one or several entries
• Open an entry
• Start an import or export
• Switch to form-level Files

See Views & Filtering for view configuration.

Entry detail

The header shows entry ID, status, created date, submitted date, and an active admin-edit indicator. Four tabs organise the record:

• Answers — values rendered against the entry’s stored form version
• Revision History — initial submission and subsequent tracked changes
• Workflow Runs — trigger, status, timing, step count, error, and diagnostics
• Files — uploaded and generated entry files

If metafields are configured, their editable form and separate revision history appear alongside the main record.

Edit a completed entry

1. On Answers, select Edit Entry.
2. Edit the form version that was used to create the entry.
3. Optionally enter a reason.
4. Select Save Changes, or Cancel to discard the edit session.

Saving first flushes pending answer changes, then completes the admin edit and creates a revision. The entry remains complete. The interface only offers this edit flow for complete entries.

An active edit is recorded with its start time and user. Other admins can see that the entry is being edited.

Metafields

Metafields save independently from main answers and are intended for internal operational state. Switching from the metafield editor to its history flushes pending values and closes the edit batch. See Metafields.

Workflow runs

The list includes workflow name, trigger label/type, status, start time, duration, executed step count, and top-level error. Open a run for step-level inputs, outputs, transitions, timing, and failures.

Use runs to answer “what automation actually happened?” rather than inferring it from entry status. See Workflow Runs.

Delete entries

Delete from the entry table, including batch deletion of selected entries. Deleting an entry removes it from active use together with its metafields and associated files.

There is no restore or duplicate-entry action in the current admin interface. Export or otherwise retain data before deleting when recovery matters.

Answer paths

Answers are a flat map:

{
  "email": "[email protected]",
  "address.city": "Leeds",
  "line_items[item_a].quantity": 2
}

The entry also retains its version, validation state, field/page visibility, and resolved content. Use the reference picker for normal builder work and References & Data for exact paths.

Bulk work

• Use views to select exactly what an export contains.
• Use CSV import to create rows or update entries by ID.
• Track background imports, exports, and error reports in form Files.

Continue with Import & Export.