n8n - 💡(How to fix) Fix N8N Form Node does not open

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

What is the error message (if any)?

There is no standard error message shown in the workflow execution.

  • error: all
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the Problem

I am using self-hosted n8n in Docker.

I have a workflow where a Form Trigger node starts the workflow, then the execution goes into a Switch node. Depending on the submitted form data, the Switch correctly routes the execution to a specific branch.

On one of the Switch branches, I connected an n8n Form node. The intention is that after the first form is submitted through the Form Trigger, the workflow should continue and open/display the next Form node to the user.

However, when the workflow execution reaches the Form node through the Switch branch, the Form node does not open/display in the browser. The workflow appears to stop at that Form node.

When I double-click the Form node in the editor, it says:

Waiting for input...

The issue appears to happen specifically when the Form node comes after a Switch node that is connected to a Form Trigger workflow path.

Expected behavior

After the user submits the Form Trigger form, and the Switch node routes the execution to the correct branch, the next Form node should open/display normally so the user can continue submitting the next step of the form workflow.

Actual behavior

The Form node does not open/display. It remains stuck/waiting, and the user does not see the next form page. In the editor, the Form node shows:

Waiting for input...

Steps to reproduce

  1. Create a workflow with a Form Trigger node.
  2. Connect the Form Trigger node to a Switch node.
  3. Configure the Switch node so that one branch routes to a Form node.
  4. Open the Form Trigger URL and submit the first form.
  5. Confirm that the Switch condition is matched and execution is routed toward the Form node.
  6. Observe that the next Form node does not open/display.
  7. Double-click the Form node in the editor.
  8. It shows Waiting for input....

Additional context

This is happening on a self-hosted Docker installation of n8n running in production. The workflow is intended to create a multi-step form flow where the first Form Trigger collects initial data, the Switch decides the next route, and the following Form node collects additional information based on the selected route.

The problem is not that the Switch condition fails. The execution appears to reach the correct branch, but the Form node does not render/open for the user.

What is the error message (if any)?

There is no standard error message shown in the workflow execution.

The visible message on the Form node is:

Waiting for input...

Please share your workflow/screenshots/recording

<img width="1852" height="816" alt="Image" src="https://github.com/user-attachments/assets/48dad8d1-7ead-40ee-bca1-bf125146a835" /> <img width="1852" height="816" alt="Image" src="https://github.com/user-attachments/assets/92ad5670-c7bf-4935-9110-03f540aad9d5" />

Debug info

core

  • n8nVersion: 2.20.7-exp.0
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 192 hours
  • maxCount: 30000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/148.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-05-17T17:02:31.702Z

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

After the user submits the Form Trigger form, and the Switch node routes the execution to the correct branch, the next Form node should open/display normally so the user can continue submitting the next step of the form workflow.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix N8N Form Node does not open