> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dforms/builder/autosave-and-publishing.md).

# Autosave, drafts & publishing

How dForms saves your work and publishes it: the save status, the Publish button and its states, why Publish can be blocked, automatic retries, recovery of unsaved changes, save conflicts and revertin

You never click Save in the editor. Every change is written to a draft automatically, and the draft stays private until you click **Publish**. This page explains the save status in the top bar, the **Publish** button and each of its states, what happens when the connection drops or someone else edits the same form, and how to go back to an earlier version.

***

## Autosave and the save status

**Step 1:** Make any change in the editor. The save status at the right of the top bar, beside **Preview**, switches to **Saving…** and, a moment later, to **Saved**. While that save is on its way, the **Publish** button says **Saving…** too.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-8f2241a567b34bfc64337d00fba9a0d0d4994ff7%2Fforms-autosave-and-publishing-01-saving.png?alt=media" alt="The right side of the editor top bar with the save status and the Publish button both reading Saving…"><figcaption><p>About one second after you stop typing, the draft is sent to the server. Publishing waits for it.</p></figcaption></figure>

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-fb01b06d27f0c25eb9ecdbb159457c12fe162b4e%2Fforms-autosave-and-publishing-02-saved.png?alt=media" alt="The right side of the editor top bar with the save status reading Saved and the button reading Published"><figcaption><p><strong>Saved</strong> means the draft is stored. Whether it is live is what the <strong>Publish</strong> button says.</p></figcaption></figure>

| Status              | Meaning                                                                                                                                                                                                                  |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Draft**           | The form has no questions yet. Nothing to save or publish.                                                                                                                                                               |
| **Saving…**         | Your last change is being written to the server.                                                                                                                                                                         |
| **Saved**           | The draft is up to date on the server.                                                                                                                                                                                   |
| **Partly saved**    | Everything is saved except one integration on the **Connect** tab, such as a webhook switched on with no URL. Hover the status to read which. See [The Connect tab saves on its own](#the-connect-tab-saves-on-its-own). |
| **Retrying…**       | The last save did not reach the server (for example your connection dropped). Your changes are kept in the browser and the save is retried automatically.                                                                |
| **Not saved**       | The server refused the save, or a change is not valid yet. Hover the status to read the reason.                                                                                                                          |
| **Saved elsewhere** | Someone else, or another tab, saved this form while you were editing. Nothing is saved until you choose a version. See [If someone else saves the same form](#if-someone-else-saves-the-same-form).                      |

The status shows the worse of two saves: the questions and design you edit, and the integrations on the **Connect** tab. On a window narrower than 1280 pixels the status is hidden, and the **Publish** button is the signal to watch.

When a save cannot reach the server, an error message tells you: **Can’t reach the server. Your changes are kept and saving will retry automatically.** When the server refuses a save or a change is not valid yet, the message (and the status tooltip) reads **Couldn’t save: {reason}**. Fix the field and the save goes through.

> **💡 Tip:** Closing the tab while a save is pending is safe: the editor flushes the last change on the way out, and it also keeps a local backup of your work.

### The Connect tab saves on its own

Integrations on the **Connect** tab (webhooks, HubSpot and the other integrations) are not part of the draft. They save straight to the live form, through their own save, and report it in a pill at the bottom right of the **Connect** tab: **Changes saved automatically** when a change lands, **Connection lost: retrying…** while it retries.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-79691bf06e4979ab71f4d5b452d5bd2cc3c7986b%2Fforms-autosave-and-publishing-10-connect-pill.png?alt=media" alt="The Connect tab with a webhook switched on without a URL: the save pill at the bottom right says everything except the webhook was saved, the Connect tab carries a dot and the top bar reads Partly saved"><figcaption><p>A webhook switched on with no URL: the pill names what was left out, the <strong>Connect</strong> tab carries a dot, and the top bar reads <strong>Partly saved</strong>.</p></figcaption></figure>

When a card is left out of the save, the pill says so, for example **Saved everything except the webhook.**, and the **Connect** tab label carries a dot until you fix it: amber while a card is left out, red when a change was lost after you left the tab. Hover the dot to read the reason. See [Delivery & retries](https://docs.dapta.ai/dforms/connect/delivery-and-retries.md) for what each integration does once a response arrives.

***

## Recovering unsaved changes

If the browser crashed, the tab was killed, or the last save never reached the server, the next time you open the form the editor shows a banner at the top: **Unsaved changes recovered**, with the text **This form has edits from a previous session that never reached the server. Restore them, or keep the saved version?**

* Click **Restore edits** to load the recovered changes into the editor (they are then saved normally).
* Click **Discard** to keep the version stored on the server and drop the local backup.

The banner only appears when the local backup differs from what the server has. If everything was saved correctly you will not see it.

***

## If someone else saves the same form

Two people, or two browser tabs, can have the same form open. Each save carries the version it started from, so one editor can never silently overwrite the other.

When the form was saved somewhere else since you last saved, your next save is refused. The save status turns to **Saved elsewhere**, and a banner at the top of the editor reads **This form was saved from somewhere else**: *Another person, or another tab, saved this form while you were editing. Your edits here are not saved yet.* Nothing more is saved until you pick one of its two buttons:

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-17d1f36d13ffb62ef8567852ea643ce2f4b7815b%2Fforms-autosave-and-publishing-05-conflict-banner.png?alt=media" alt="The editor with the red banner This form was saved from somewhere else, its See saved version and Keep mine buttons, and the save status reading Saved elsewhere"><figcaption><p>The conflict banner. Nothing is saved until you choose a version.</p></figcaption></figure>

* **See saved version** reloads the editor with the version saved elsewhere. Your edits from this tab are not thrown away: the **Unsaved changes recovered** banner offers them back.
* **Keep mine** keeps your edits, and your next save overwrites the other version.

**Publish** is blocked the same way until you choose: its tooltip reads **This form was saved from somewhere else. Choose which version to keep before you publish.** Changes you make yourself outside the draft, such as a new link from **Edit link** or a HubSpot mapping saved from the question panel, never trigger the banner.

***

## Draft versus published

Saving and publishing are two different things:

* **Draft**: what you see in the editor and in **Preview**. Every autosave updates it.
* **Published**: what respondents see at your public link and in embeds. It only changes when you click **Publish**.

A form is live from the moment you create it: its public link answers right away with what the form was created with. Every edit after that goes to the draft, and **Publish** pushes the draft to the live form.

**Step 2:** As soon as the draft differs from the live form, an amber **Unpublished changes** chip appears next to the form name and the button turns into a green **Publish**.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-3a088d0990f940f1ec60144b17c6b3beafb27b4c%2Fforms-autosave-and-publishing-03-unpublished-badge.png?alt=media" alt="The editor top bar with the Unpublished changes chip next to the form name and the green Publish button"><figcaption><p>The chip tells you the live form is behind your draft.</p></figcaption></figure>

**Step 3:** Click **Publish**. If an edit is still being saved, **Publish** waits for that save first, so what goes live is exactly what you see. The button reads **Publishing…** for a moment.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-de01f66dc6dd16d7bf9cf2a59df2848e2946f5ff%2Fforms-autosave-and-publishing-07-publishing.png?alt=media" alt="The Publish button reading Publishing… with a spinner"><figcaption><p>The draft is on its way to the live form.</p></figcaption></figure>

Then a toast confirms **Changes published. Your form is live.**, the chip disappears and the button reads **Published** with a check mark.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-7dd8b0a4e69880d858d6649cf660ce091a021dbe%2Fforms-autosave-and-publishing-04-published-toast.png?alt=media" alt="The editor after clicking Publish, with the confirmation toast Changes published. Your form is live. and the button reading Published"><figcaption><p>Publishing copies the draft to the live form. Keep editing afterwards: new edits stay private until the next Publish.</p></figcaption></figure>

If that last save fails, nothing is published and the message reads **Your latest changes could not be saved, so nothing was published. Try again once they save.** If the publish itself goes wrong you will see **Could not publish. Please try again.** Your draft is not lost in either case; click **Publish** again.

### What the Publish button says

| Button                           | What it means                                                   | Can you click it?                                             |
| -------------------------------- | --------------------------------------------------------------- | ------------------------------------------------------------- |
| **Publish**, green               | The draft has changes the live form does not have.              | Yes: it publishes them.                                       |
| **Saving…**, with a spinner      | An edit is on its way to the server.                            | Not yet. It turns into **Publish** as soon as the save lands. |
| **Publishing…**                  | The draft is being published.                                   | No.                                                           |
| **Reverting…**                   | An earlier version is going live again.                         | No.                                                           |
| **Published**, with a check mark | The live form is the draft. Nothing to publish.                 | No.                                                           |
| **Publish**, blocked             | A save is failing or in conflict, or the form has no questions. | No. It tells you why.                                         |

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-f135f0af7182206da778eeb3f233b4a78fa379ee%2Fforms-autosave-and-publishing-08-published.png?alt=media" alt="The Published button with its tooltip All changes are published"><figcaption><p><strong>Published</strong>, and the tooltip that explains it.</p></figcaption></figure>

**Why Publish is blocked.** Hover the button, focus it with the keyboard or tap it on a phone, and a tooltip under it gives the reason:

| Tooltip                                                                                       | When                                                                   |
| --------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| **All changes are published**                                                                 | Nothing is pending.                                                    |
| **Saving your changes. You can publish as soon as they are saved.**                           | An edit is on its way to the server.                                   |
| **Your changes are not saved yet. Trying again.**                                             | The save did not reach the server and is being retried.                |
| **Your changes could not be saved. You can publish once they are saved.**                     | The server refused the save. Fix the change the save status points to. |
| **This form was saved from somewhere else. Choose which version to keep before you publish.** | A save conflict. Pick a version in the banner first.                   |
| **Add a question first. Then you can publish.**                                               | The form has no questions. The save status reads **Draft**.            |

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-a7ec9921db6903a16907ee264d62fb335ecfc3dc%2Fforms-autosave-and-publishing-09-blocked-empty.png?alt=media" alt="A form with no questions: the save status reads Draft and the tooltip under Publish says Add a question first. Then you can publish."><figcaption><p>A form with no questions cannot be published. The tooltip says what to do.</p></figcaption></figure>

On a phone, a tapped tooltip goes away on the next tap elsewhere, on a scroll, or after a few seconds.

## Revert to the previous version

Published something by mistake? The arrow on the right half of the button opens **Publish options** with **Revert to the previous published version**, and under it the date that version went live (**Published on {date}**).

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-e40fc28721d00996b4b9755a8e9d215c55264be5%2Fforms-autosave-and-publishing-06-publish-menu.png?alt=media" alt="The menu next to Publish open, with Revert to the previous published version and the date it was published"><figcaption><p>One step back. It is greyed out with <strong>No earlier published version yet</strong> on a form published only once.</p></figcaption></figure>

Click it and confirm with **Revert**. The earlier version goes live again and the one that was live becomes the previous version, so reverting a second time undoes the revert. Your draft does not change, and the integrations under **Connect** stay as they are. While it runs, the button reads **Reverting…**, and then **The previous version is live again.** confirms it.

## Good to know

| Topic               | Behavior                                                                                                                                                                                                                                                                            |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A new form          | A form answers at its public link as soon as you create it, with what it was created with: the questions of a template, or, for a blank form, an empty page reading **This form has no steps yet.** Questions you add afterwards are a draft until you click **Publish**.           |
| Editing a live form | Respondents keep seeing the last published version while you work. Nothing changes for them until you publish.                                                                                                                                                                      |
| Integrations        | Integrations you switch on under **Connect** > **Integrations** apply to the live form immediately; they do not wait for Publish. Tracking IDs under **Tracking & pixels** and the **Spam protection (captcha)** setting are part of the draft and go live when you publish.        |
| Unpublishing        | There is no Unpublish button. To take a form offline, delete it from the **Forms** list (this also deletes its submissions), or duplicate it first if you want to keep a copy.                                                                                                      |
| Duplicates          | **Duplicate** in the Forms list creates "{name} (copy)" from the original's **published** version, in the same folder. The copy answers at its own link right away, and edits the original has not published yet are not copied. Edit the copy and **Publish** it when it is ready. |
| Who can publish     | Every member of the workspace can create, edit and publish forms.                                                                                                                                                                                                                   |

## What's next

* [Preview on desktop, tablet and mobile](https://docs.dapta.ai/dforms/builder/preview.md): check the draft before you publish.
* [Delivery & retries](https://docs.dapta.ai/dforms/connect/delivery-and-retries.md): what happens to each response after it is submitted.
* [Publish, Share & Embed](https://docs.dapta.ai/dforms/share.md): copy the link, embed the form, share card.
* [Create a form](https://docs.dapta.ai/dforms/builder/create-a-form.md): duplicate and delete forms from the list.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/dforms/builder/autosave-and-publishing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
