The draft
Every form has exactly one draft — a mutable, private working copy of the form graph. The draft is never seen by respondents. It is what you edit in the Studio.- The draft exists from the moment a form is created.
- Saving the draft does not affect the live form.
- The draft always reflects your most recent edits.
Autosave
The Studio automatically saves the draft every 15 seconds while you are working. The save status indicator in the top bar always reflects the current state:| Status | Meaning |
|---|---|
| All changes saved | The draft is fully persisted |
| Unsaved changes | Edits exist that have not been saved yet |
| Saving… | An autosave or manual save is in progress |
| Save failed | The save request failed — hover for the error detail |
Manual save
Press Cmd + S (Mac) or Ctrl + S (Windows/Linux) at any time to save the draft immediately. The Save button in the top bar does the same thing and is disabled when there are no unsaved changes.Publishing
Publishing creates an immutable published version — a permanent snapshot of the graph at the moment you clicked Publish. Once published, that version never changes. What happens when you publish:- Feedal validates the graph (entry node set, fallback end node set, no orphan nodes, etc.).
- If validation passes, a new version is created and becomes the live form immediately.
- The draft continues to exist independently — you can keep editing without affecting the live version.
- The Results button appears in the top bar if it was not visible before.
Versions
Every time you publish, Feedal creates a new version with an incrementing version number (v1, v2, v3, …). Versions are permanent — they cannot be edited or deleted.| Property | Draft | Published version |
|---|---|---|
| Editable | Yes | No |
| Respondents can fill it out | No | Yes |
| Visible to you | Yes (Studio) | Yes (Results hub) |
| Responses attached | No | Yes |
| Count per form | Always exactly 1 | One per publish |
When you publish a new version, existing respondents who have an
in-progress session on the previous version are not affected — they
continue on the old version. Only new visitors see the new version.
Version history
The Version history tab in the Results hub shows every published version with its publish date, node count, and edge count. Selecting a version shows the responses collected specifically on that version.Next steps
Publishing your form
Review the Publish button and what validation errors look like.
Keyboard shortcuts
Save with Cmd/Ctrl + S and undo with Cmd/Ctrl + Z.