Forms troubleshooting and FAQ
A form is not in the catalogue
Section titled “A form is not in the catalogue”Confirm you opened the owning service and selected Forms under Process Modules. Check service membership and content access. A published form still belongs to its source service. See Manage forms and pages.
Save does not complete
Section titled “Save does not complete”Look for invalid field names, unsupported imported types, incomplete required metadata, or an open editor dialog. Close exploratory dialogs with Cancel, correct the highlighted item, and save again. Use the canonical type names offered by the palette in the field type reference.
A page title looks generic in Preview
Section titled “A page title looks generic in Preview”Select the section and set Section Title. The internal section label and visible section title are separate properties. Rename the page tab separately for the step label. See Manage forms and pages.
Required errors remain after correction
Section titled “Required errors remain after correction”Move focus away from the corrected field, then try navigation again. Check conditional required rules, repeater rows with required child fields, and hidden fields. A hidden field that is still required cannot be satisfied; Use variables and rules covers testing both branches.
Preview and published output differ
Section titled “Preview and published output differ”Confirm the draft was saved and republished. Check the published form version, engine, Forms theme or locked Brand version, language, and regional context. Submitted-response playback intentionally uses the stored historical version, as explained in Rendering and form engines.
A date or time looks wrong
Section titled “A date or time looks wrong”Inspect the form regional policy and the Preview locale/time-zone overrides. Confirm whether the field represents a calendar date, time of day, local date-time, or instant. Test daylight-saving boundaries when relevant. See Configure settings and localization.
A repeater cannot remove its first row
Section titled “A repeater cannot remove its first row”Review Minimum Repetitions. A row at the minimum cannot be removed. Required nested fields can also block page navigation when a default row exists. Repeater settings are listed in the layout reference.
Generate Schema shows unexpected work
Section titled “Generate Schema shows unexpected work”Compare field names, table prefix, repeater names, and the last saved version. Renaming a storage identity can create a new column and leave the old one unlinked. Review the difference rather than deleting historical data automatically. See Manage versions, schema, and storage.
Unlinked columns appear
Section titled “Unlinked columns appear”They usually represent renamed or removed historical fields. Confirm retention and reporting needs. If the active field should map to the column, correct the field name or schema relationship and regenerate. Form data model and storage explains why the old column survives.
View Published Form is unavailable
Section titled “View Published Form is unavailable”Save the draft, enable the intended publisher, confirm Internal access or external publisher configuration, then Publish. A failed destination does not produce a successful link. See Publish, submit, and recover.
The completion page does not appear
Section titled “The completion page does not appear”Confirm engine 1.1.0, a submission-complete page, and a Show completion page action. The page appears only after storage succeeds. If submission fails, correct the error while preserving the respondent’s answers.
A draft cannot be restored
Section titled “A draft cannot be restored”A draft saved by a newer version of the form is refused rather than partially applied. A draft from an externally published form exists only as a file on the respondent’s device. Check the retention window and whether the form has changed since the draft was saved. See Let respondents save and return later.
A file or signature link fails
Section titled “A file or signature link fails”Confirm the viewer is authorized for the service/form response and that the object still exists. Do not copy the guarded object URL into public documentation or an anonymous channel.
Response count and analytics disagree
Section titled “Response count and analytics disagree”The card and submissions table reflect stored records. Analytics reflects tracked events and can use a separate update cadence or filter. Check service and date filters, then use View Data to confirm persistence. Metric definitions are in the submissions and analytics reference.
An AI-generated form is incomplete
Section titled “An AI-generated form is incomplete”AI output is a proposal. Review page structure, field types, storage names, validation, consent, access, and completion behavior. Regenerate or edit the draft before saving and publishing. Build with the AI assistant lists what to check.