Publish checks
While you edit, Formstep lists what would not work once the form is live. Errors block publishing; warnings ask you to confirm.
Where to find the checks
Your edits save as a draft, and respondents see the last published version until you click Publish. The issue indicator beside Publish is green when all is well, amber for warnings, and red for errors. Click it to see the list, and click an entry to go where you fix it. The list updates as you type.
Errors and warnings
| Level | What happens when you press Publish |
|---|---|
| Error | Publishing stops, and nothing goes live. The same checks apply when an automation or AI agent publishes. |
| Warning | A Review needed dialog lists the warnings. Fix them, or click Publish to go ahead. |
For a settings warning, Publish also applies the fix the warning names, such as turning off a password gate that has no password. You fix content warnings yourself.
Common errors
| Message | How to fix |
|---|---|
| Variable “Email” references a deleted field and will show as empty. | An @ mention points at a question you deleted. Remove the mention or pick another question. |
| A reference points to a field that no longer exists. | An email, a redirect parameter, an integration, or a translation still uses a deleted question. The entry names the place to update. |
| A logic rule references a deleted field or page. | Update or remove the rule. The Logic tab lists it under Needs attention. |
| Field key “total” is used by more than one field. | Give each field its own key in the Fields tab. See Field keys. |
| Complete setup for this Payment question before publishing. | Set a currency and amount, and connect Stripe. See Payment collection. |
| Connect Cal.com before publishing forms that schedule appointments. | Connect Cal.com and pick an event type. See Cal.com. |
Common warnings
“Page 2 has no content respondents can see.” The page holds only logic or hidden blocks, so respondents would walk into a blank step. Add content or remove the page break.
“A page jump sends respondents back from Page 3 to Page 2.” Respondents could loop between the two pages. Similar warnings flag a jump that targets its own page, or one on the last page, where Next submits the form. Review the rule.
“Field key “company_name” will no longer exist after this publish.” Workflows that read it stop getting that answer. See When a key is about to disappear.
“French: 12 strings missing.” Some text has no translation yet, or changed after it was translated. See Multilingual forms.
- “Slack connection expired.” The form publishes, but submissions stop reaching that app until you reconnect it.
“The decision question has no approve, decline or changes option.” Requests would finish with no outcome. Insert a Decision question from the / menu.
Settings that Publish fixes for you
When you publish anyway, Formstep turns these settings off or cleans them up:
- A password gate with no password is turned off, so respondents can open the form.
Edit after submit is turned off on a form that does not allow it.
- New-submission notifications with no valid address are turned off, and invalid addresses are dropped from the list.
- A confirmation or reminder email with no email question to send to is turned off.
- A redirect address that is not a valid web address is cleared, and respondents see your thank-you page.
Other reasons a publish is refused
These appear as a red notification when you press Publish:
- The form is in the trash. Restore it first.
An email question has respondent email verification switched on and the workspace owner's plan is not Business. Upgrade, or switch verification off.
- A field key you typed is already published on another field. Give each field its own key and publish again.