❔ Catch-up quick
When a Form Journey encounters a problem, GoFormz displays an error so you can identify what went wrong. Some errors are visible to both Form Users and admins. Most require an admin to resolve.
Where errors appear
Form Journey errors surface in two places:
Forms list — A ⚠️ icon appears to the right of the Form name (or to the right of the lock icon, if the Form is also locked). This is visible to both Form Users and admins.
Form Editor — Open the Form and select the Errors tab in the panel at the top right of the screen. The panel groups Form Journey issues under a Form Journey Error header and shows a count of active errors alongside any other errors on the Form (such as incomplete required fields).
🗒️ Note: Form Journey requires GoFormz mobile app Version 4.0.2436 or later. If a journey-enabled Form isn't behaving as expected on mobile and no error appears, confirm the app is up to date before troubleshooting further.
Form Journey error types
Assigned Recipient Not Found
Error message: The user or group this form is being transferred to "[username or Group ID]" wasn't found. The identifier may be incorrect, outdated, or sourced from the wrong field. Contact your admin to verify.
What it means: The Form reached a Transfer step, but the intended recipient — a specific user or group — no longer exists in the system or couldn't be matched. This can happen if a user was removed from the account, a group was deleted, or if the recipient is being pulled from a Form field that contains an incorrect or outdated value.
Who can resolve it: Admin.
How to resolve it:
Open the affected Template in the Template Editor.
Select the Form Journey tab and locate the Transfer step.
Verify the recipient is a valid, active user or group.
If the recipient is pulled from a Form field, confirm the field is correctly mapped and contains a valid value.
Update the step configuration if needed, then save and republish the Template.
If the Form is already stuck, an admin may need to manually reassign or unlock it.
Journey Step No Longer Exists
Error message: This form is stuck because the journey step it was on no longer exists in the current template version. Contact your admin.
What it means: The Template was updated and republished after this Form started its journey. The step the Form was on was removed in the new Template version, so the journey no longer knows where to send it.
Who can resolve it: Admin.
How to resolve it:
If the step was removed intentionally, the admin will need to manually advance or reopen the affected Form. The Form cannot automatically resume the journey.
To prevent this from happening to future Forms, finalize your Form Journey configuration before Forms begin using a Template. See Build a Form Journey for guidance on managing journey changes safely.
🗒️ Note: This error is a known risk when editing a live journey. Always review in-progress Forms before republishing a Template with journey changes.
Deactivated Workflow
Error message: This form journey has stalled because the workflow "[Workflow Name]" is currently deactivated. Contact your admin.
What it means: The Form reached a Trigger a Workflow step, but the Workflow configured for that step has been deactivated. The journey cannot continue until the Workflow is active again.
Who can resolve it: Admin.
How to resolve it:
Select the [Workflow Name] link in the error panel — this takes you directly to the affected Workflow in the Workflow Editor.
Reactivate the Workflow, or replace it with an active Workflow.
If you replace the Workflow, update the Trigger a Workflow step in the Template Editor and republish.
Once the Workflow is active, the journey will resume for affected Forms.
Workflow Failure
Error message: This form journey has halted because the workflow "[Workflow Name]" failed.
What it means: The Form reached a Trigger a Workflow step with Halt journey on workflow failure enabled, and the Workflow failed. The journey cannot advance until the Workflow completes successfully.
Who can resolve it: Admin, or the Form User by resubmitting the Form.
How to resolve it:
Option 1 — Resubmit the Form:
The Form User opens the Form and resubmits it.
This fires a new Workflow job. If the new job succeeds, the journey advances to the next step.
Option 2 — Rerun the Workflow (admin):
Select the [Workflow Name] link in the error panel to open the Workflow Editor.
Navigate to Workflow Jobs and locate the failed job.
Rerun the job. If it succeeds, the journey advances to the next step.
🗒️ Note: This error only appears when Halt journey on workflow failure is enabled on the Trigger a Workflow step. If that setting is off, a Workflow failure does not halt the journey or display an error.
Public Form Delivery Error
Error message: The system couldn't send this form to "[email address / phone number]." The recipient's contact information is invalid or incorrectly formatted.
What it means: The Form reached a Send a Form (Public Form) step, but the system couldn't deliver it because the recipient's email address or phone number is invalid or incorrectly formatted.
Who can resolve it: Admin, or the Form User who entered the recipient's contact information.
How to resolve it:
Open the Form and check the field used to populate the recipient's contact information.
Correct the email address or phone number to ensure it is valid and correctly formatted.
Save the Form. The system will attempt to resend once the contact information is corrected.
🗒️ Note: If the recipient's contact information is pulled from a Form field, the Form User filling out the Form is responsible for entering a valid value. Admins should verify the correct field is mapped in the Send a Form step configuration.
Journey Connection Error
Error message: This journey can't run because of connection errors in the flow. Contact your admin.
What it means: The Form Journey has a configuration problem in the Template Editor — one or more steps, branches, or outcomes are not connected. This is an admin-side issue that must be fixed before the journey can run.
Common causes:
A step has been added to the canvas but not connected to the previous or next step
An Approval step's Approve or Deny branch has no connection
A Conditional step has an unconnected branch outcome
Who can resolve it: Admin.
How to resolve it:
Open the affected Template in the Template Editor.
Select the Form Journey tab.
Review the canvas for any steps, branches, or outcomes missing a connection — these will appear visually disconnected.
Connect all steps and branches so the journey has no dead ends.
Save and republish the Template.
🗒️ Note: Forms in progress when this error occurs will clear the Journey Connection Error once the Template is republished with all connections in place.