Form Trigger ×4 → single “Form ending” node throws “Referenced node is unexecuted”

[makhataibar]

In one workflow I now have three Form Trigger nodes:

• Test form 1

• Test form 2

• Test form 3

All three merge into a filter test-id is not empty and then go through the same chain:

get test → haven’t n8n_test_form_url → prepare test answer → save test answer → prepare test answers for AI → prepare prompt → generate test result → prepare test result → save test result → create jira task → Form ending

The last node is a Form (operation: completion) that should show the AI result back to the user.

Problem

After adding multiple Form Triggers, the workflow intermittently fails with:

ExpressionError: Referenced node is unexecuted

Stack trace excerpt (Cloud 1.94.1):

ExpressionError: Referenced node is unexecuted
  at createExpressionError ... WorkflowDataProxy.ts:774
  at ensureNodeExecutionData ... WorkflowDataProxy.ts:1081
  ...
  at Form.webhook ... Form.node.ts:338

Expected

A single Form ending should be able to serve as a completion screen for multiple Form Triggers that feed into the same path, as long as the data flows through.

Actual

Form ending always can’t resolve expressions that reference other nodes in the same executed path and throws “Referenced node is unexecuted”.

Questions

1. Is it unsupported to have multiple Form Trigger nodes feeding into a single Form (completion) node?

2. Is “Referenced node is unexecuted” expected when expressions reference nodes outside the current branch, even if those nodes are on the line for this trigger?

Environment

• n8n Cloud 1.94.1 (binaryDataMode: filesystem)

• Node throwing error: Form ending (Form node v1, operation: completion)

• OpenAI node before it, Firestore upserts, etc. (can share full JSON if needed)

Minimal repro (trimmed)

"nodes": [
  { "type": "n8n-nodes-base.formTrigger", "name": "Test form 1" },
  { "type": "n8n-nodes-base.formTrigger", "name": "Test form 2" },
  { "type": "n8n-nodes-base.formTrigger", "name": "Test form 3" },

  { "type": "n8n-nodes-base.filter", "name": "test-id is not empty" },

  { "type": "n8n-nodes-base.set", "name": "prepare test result" },
  { "type": "n8n-nodes-base.googleFirebaseCloudFirestore", "name": "save test result" },

  { "type": "n8n-nodes-base.form", "name": "Form ending",
    "parameters": {
      "operation": "completion",
      "completionTitle": "The end",
      "completionMessage": "={{ $('save test result').item.json.result }}"
    }
  }
]

Would love guidance on whether this is a bug, a known limitation of cross‑node references with multiple triggers, or a pattern issue on my side. Thanks!

[jabbson]

Hey @makhataibar hope all is well, welcome to the community.

Could you please include your workflow or an example of a workflow that doesn’t work?

[makhataibar]

[makhataibar]

When the workflow is triggered from On form submission, everything works as expected.

However, when it’s triggered from On form submission1 (which is another Form Trigger in the same workflow), the Form Ending node throws the error:

ExpressionError: Referenced node is unexecuted

The workflow structure and expressions are identical for both triggers — the only difference is which trigger starts the execution.

[jabbson]

I see what the problem is, not sure if this behaviour is intended. Please create a bug about this here, or if this is not something you want to do or are comfortable doing, let me know, I can do it for you.

[makhataibar]

Form completion node throws ‘Referenced node is unexecuted’ when triggered from a second Form Trigger