Form-Based Workflow Fails to Progress After Upgrading to n8n 1.67.1

It sounds like you’re experiencing an issue where your multi-step form isn’t automatically progressing to the next page after the upgrade. This isn’t intended behavior—once activated, a workflow using the Form Trigger and subsequent Form nodes should advance without requiring you to manually “nudge” it via the /form-waiting/ URL.

Below are a few troubleshooting suggestions and points to check:

1. Verify Workflow and URL Usage
• Make sure you’re running the workflow in production mode and using the Production URL from the Form Trigger. (When testing via the editor’s Test URL, behavior may differ.)
• Double-check that the workflow is activated immediately after you upgrade and that no previous execution is blocking progress.

2. Review Execution Order and Multi-branch Configurations
• Since n8n 1.x introduced changes in execution order for multi-branch workflows, review your workflow to ensure it follows current best practices. If the next form page isn’t receiving the expected input, it might be related to how your branches are configured.
• Confirm that any conditional logic between form pages isn’t inadvertently stalling the flow (for example, awaiting input that isn’t provided).

3. Check for Error Messages or Unexecuted Nodes
• Although the error message about a node not executing isn’t mentioned explicitly here, it’s a good idea to inspect the Executions tab for any hints that a previous node didn’t run (refer to the troubleshooting guidance for “referenced node is unexecuted” in the docs).
• If a node is being skipped because it wasn’t triggered, that might explain why the next form page isn’t automatically loaded.

4. Report or Look for Updates
• There isn’t any official documentation noting that manual progression via the /form-waiting/ endpoint is required, so if your configuration is otherwise correct, this may be an unintended regression.
• You might consider checking the n8n community forum or GitHub issues to see if others are reporting the same behavior. If nothing similar appears, then opening an issue with your workflow details (while sharing only sanitized information) could help the n8n team investigate further.

Workaround:
Until a fix is available, manually progressing by navigating to the /form-waiting/ URL is an acceptable temporary workaround.

If none of the above helps, please consider providing additional details (such as workflow screenshots or JSON snippets, minus any sensitive data) on the community forum or in a GitHub issue so that the team can dig into the problem further.

Let me know if you need more guidance on configuring or troubleshooting your Form nodes!