Multi-Stage Forms not working - 404 Error

Describe the problem/error/question

When attempting to leverage a multi-stage form, the Form Ending and Next form nodes attempt to take the process to https://myn8nurl.com/form-waiting/253443 which always receives a 404 Error

What is the error message (if any)?

Oops, couldn’t find that
404 Error

Information on your n8n setup

  • n8n version: 1.72.1
  • Database (default: SQLite): postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): undefined
  • Running n8n via (Docker, npm, n8n cloud, desktop app): google cloudrun
  • Operating system: GCP
1 Like

Hey @Dan_Westness

Mind sharing the workflow so we can take a look? Does the same workflow work on regular cloud if you try it?

Here is the simple workflow
After some additional review this appears to be an issue with queue mode and workers.

I setup a new vanilla n8n instance in my local docker lab and have observed this:

With this config (note: I do have multiple workers available):

      EXECUTIONS_MODE: queue
      N8N_DISABLE_PRODUCTION_MAIN_PROCESS: true

The form will not load at all from production url. Page ends up with 404:
image

With this config (note: I do have multiple workers available):

      EXECUTIONS_MODE: queue
      N8N_DISABLE_PRODUCTION_MAIN_PROCESS: false

The form will display but gets stuck spinning endlessly on the submit button while the execution log shows an error
– OR –
I may receive the error “Problem submitting response” while the execution history shows the workflow stuck in “Waiting” status with the “Form End” node spinning in wait until it eventually timesout.

image
image

With this config everything works as expected

      EXECUTIONS_MODE: regular
      N8N_DISABLE_PRODUCTION_MAIN_PROCESS: false

image

Here is the sample test workflow i’m using for reference as well

I have the same issue with the Conversational Interviews with AI Agents and n8n Forms | n8n workflow template template. Just spinning wheel on Clicking the button on the first form.

I’m using version 1.81.4 in queue mode and facing the same issue. Did you find a fix or workaround?

Hi, I found a fix for this. I’m using Nginx, and the solution was to route /form/ and /form-waiting/ traffic to the webhook node. Keep /form-test/ traffic pointed to the main node. This setup resolved the issue for me.

1 Like

Unfortunately this did not fix it for me.

This actually is working for me now. I think my previous test was invalid regarding directing form-waiting url to the webhook listener node.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.