Using the new n8n forms “next form page” nodes in the latest release, There are a few more transformation steps that I need to do in order to build the second page of my form, using dynamic values to set up some questions & answers, all in all this takes around 5 seconds between the form submission and when the second form should pop up, however the second form never pops up/overwrites the first form, so I have to trigger it manually in my workflow (Which of course wouldn’t work in any real life scenarios)
If I re-arrange the form so it’s right next to any built in nodes that run instantly and doesn’t include my API calls, it triggers the “next form page” node correctly, but it seems as if the window to trigger the second form is very small and does not allow for any further transformations.
I’m using some API calls to our CRM that extends the flow time to a few seconds.
The “next form page” node just sits there loading with the message “The node is waiting for a form submission”. even though this has been done.
Thanks for posting here and welcome to the community!
Can you please update your n8n version and try again? We’ve recently fixed a bug related to this:
If the issue still persists, could you share your workflow ideally with some dummy data, so we can try to reproduce it?
Tip for sharing your workflow in the forum
Pasting your n8n workflow
Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.
```
<your workflow>
```
Make sure that you’ve removed any sensitive information from your workflow and include dummy data or pinned data as much as you can!
I am running on version 1.66.0 and the issue still occurs. The workflow that hangs:
To add some info - when testing the workflow, it also hangs after submitting the first page of the form, but if I then manually go to the test URL of the second page it finishes the workflow successfully (with the correct values loaded into the second page).
Hi, updated today also to 1.67.1, short workflow, trigger form → next form page → form ending. take 1 minute until the next page is shown, somtimes it doesnt load anything
If it helps, I’ve just tested in the cloud version and it does work for me there. Also, I tried with 1.68.0 locally and no luck.
Some more information - while looking at the browser dev tools, I found that the first form page does request http://localhost:5678/form-waiting/84, but for some reason it does not redirect…
Same here. Pending forever. Docker on Linux. Latest n8n-docker image (1.68.0). WEBHOOL_URL set correctly.
What also looks odd to me is that the next form node waits for a url with an integer. I also had situations (when using the production form url) where instead of this integer null was shown.
Hopefully the great n8n team can fix this soon!
Ok I got it running after I’ve set up the WEBHOOK_URL=, but now it will not work if I put a Switch node in between. The error output is:
Referenced node is unexecuted
n8n version
1.68.1 (Self Hosted)
Stack trace
ExpressionError: Referenced node is unexecuted at createExpressionError (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/WorkflowDataProxy.js:474:20) at ensureNodeExecutionData (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/WorkflowDataProxy.js:713:31) at Object.get (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/WorkflowDataProxy.js:812:29) at findExtendedFunction (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Extensions/ExpressionExtension.js:281:56) at Proxy.extend (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Extensions/ExpressionExtension.js:292:27) at Proxy.eval (eval at getFunction (/usr/local/lib/node_modules/n8n/node_modules/@n8n/tournament/dist/FunctionEvaluator.js:14:22), :6:47) at FunctionEvaluator.evaluate (/usr/local/lib/node_modules/n8n/node_modules/@n8n/tournament/dist/FunctionEvaluator.js:20:19) at Tournament.execute (/usr/local/lib/node_modules/n8n/node_modules/@n8n/tournament/dist/index.js:43:31) at evaluateExpression (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/ExpressionEvaluatorProxy.js:113:16) at Expression.renderExpression (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Expression.js:228:70)
Interesting! This does work around the issue for me in test mode, but doesn’t work in the production URL.
I tested multiple approaches and it seems that for me it only works via the “Test Workflow” button. So if I use the same URL in another browser window, it doesn’t work. And also, it doesn’t work in the production URL (for the same reason?).
To me, it looks like it only works in a pop-up window, and not in a standard tab.
It still doesn’t work, even when using the test URL (copied from the working pop-up). There is some magic about the way n8n opens the “Test Workflow” URL that makes it work for me.
Edit 2:
I just updated to 1.69.2, and the workaround works now for both test and production URLs.
I also tested my original workflow (without the workaround) and it still hangs.
I don’t know what might be so special about my on-prem setup but this workaround doesn’t work for me. I also set my webhook_url correctly. All my other webhooks works flawlessly. I want to use the forms-next-page feature so bad!
