# Sub workflow error: "Missing node to start execution - Please make sure the workflow you're calling contains an Execute Workflow Trigger node"

**URL:** <https://community.n8n.io/t/sub-workflow-error-missing-node-to-start-execution-please-make-sure-the-workflow-youre-calling-contains-an-execute-workflow-trigger-node/209351>\
**Category:** Questions\
**Tags:** execute-workflow\
**Created:** [October 21, 2025, 2:18pm UTC](https://community.n8n.io/t/sub-workflow-error-missing-node-to-start-execution-please-make-sure-the-workflow-youre-calling-contains-an-execute-workflow-trigger-node/209351 "2025-10-21T14:18:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Levente\_Toth](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/levente_toth/32/48043_2.png) [@Levente\_Toth](https://community.n8n.io/u/Levente_Toth)\
**Post date:** [October 21, 2025, 2:18pm UTC](https://community.n8n.io/t/sub-workflow-error-missing-node-to-start-execution-please-make-sure-the-workflow-youre-calling-contains-an-execute-workflow-trigger-node/209351/1 "2025-10-21T14:18:44Z")

</div>

## I have a self-hosted **n8n v1.115.3** instance (Docker).

Everything was working perfectly — my AI agent used the **Call Workflow (Execute Workflow)** node to call another workflow called **Event\_Check**.

Then, without any structural change to the workflows, the system suddenly started returning this error:

## Missing node to start execution

Please make sure the workflow you’re calling contains an Execute Workflow Trigger node

Since then, the sub-workflow refuses to run.

It had been working fine for weeks with exactly the same setup.

**Context**

- **Parent workflow:** AI agent orchestration pipeline (triggered by webhook)

- **Sub-workflow:** Event\_Check

- **Expected behavior:** The Execute Workflow node should call Event\_Check, wait for completion, and receive the results.

- **Actual behavior:** It fails instantly with “Missing node to start execution”.

**What I’ve checked**

1. The Event\_Check workflow **definitely contains a valid Execute Workflow Trigger** node, connected to the main branch.

2. Tried **multiple n8n builds and versions** — same issue everywhere.

3. Tried **creating new minimal workflows** :

4. Both workflows are in the same Project.

5. Tried referencing by **name** and by **ID** — no difference.

6. Restarted and rebuilt Docker containers, cleared cache, re-imported workflows.

7. No code or schema changes inside Event\_Check.

**Environment**

- **n8n version:** 1.115.3

- **Deployment:** Self-hosted (Docker)

- **Binary Data Mode:** default

- **Mode:** Run once with all items

- **Wait for completion:** Enabled

- **Source:** Database

**Observed result**

Even though Event\_Check starts with a valid “When Executed by Another Workflow” trigger, n8n refuses to execute it, reporting _“Missing node to start execution”_.

This happens across all versions tested and even with brand-new, minimal workflows.

## 

 ![Képernyőfotó 2025-10-21 - 16.16.49](https://europe1.discourse-cdn.com/n8n/original/3X/8/4/84af14d06bd498f476ae7fddbe532f4b75bd3fa8.png)

 ![Képernyőfotó 2025-10-21 - 16.02.15](https://europe1.discourse-cdn.com/n8n/original/3X/5/3/53745f6d6cf11ce9c9932d9920de53b3827f1503.png)

 ![Képernyőfotó 2025-10-21 - 16.02.03](https://europe1.discourse-cdn.com/n8n/original/3X/a/7/a76493324efe9bd672ce27a3af05c2d1630c2383.png)

 ![Képernyőfotó 2025-10-21 - 16.01.46](https://europe1.discourse-cdn.com/n8n/original/3X/8/3/83a3305e8dd09ce1610e8bd1491848d5fa072f24.png)

## Information on your n8n setup

- **n8n version: 1.115.3**
- **Database (default: SQLite):**
- **n8n EXECUTIONS\_PROCESS setting (default: own, main):**
- **Running n8n via (Docker, npm, n8n cloud, desktop app): Docker**
- **Operating system: MAC OS 15.6**

---

<div class="post-metadata">

**Author:** ![Parintele\_Damaskin](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/parintele_damaskin/32/139243_2.png) [@Parintele\_Damaskin](https://community.n8n.io/u/Parintele_Damaskin)\
**Post date:** [October 21, 2025, 2:37pm UTC](https://community.n8n.io/t/sub-workflow-error-missing-node-to-start-execution-please-make-sure-the-workflow-youre-calling-contains-an-execute-workflow-trigger-node/209351/2 "2025-10-21T14:37:05Z")

</div>

Simply remove the Call ‘Appointment dev’ final node in the subworkflow.

It will return anyway the response to the main workflow ai agent, together with the intermediateSteps(if you enabled it).

---

<div class="post-metadata">

**Author:** ![Levente\_Toth](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/levente_toth/32/48043_2.png) [@Levente\_Toth](https://community.n8n.io/u/Levente_Toth)\
**Post date:** [October 21, 2025, 3:37pm UTC](https://community.n8n.io/t/sub-workflow-error-missing-node-to-start-execution-please-make-sure-the-workflow-youre-calling-contains-an-execute-workflow-trigger-node/209351/3 "2025-10-21T15:37:07Z")

</div>

Hehe

Man you saved me a few mental breakdown 😆

But now I dont understand why was it working for the last 3 weeks with that setup.😅

---

<div class="post-metadata">

**Author:** ![Parintele\_Damaskin](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/parintele_damaskin/32/139243_2.png) [@Parintele\_Damaskin](https://community.n8n.io/u/Parintele_Damaskin)\
**Post date:** [October 21, 2025, 5:11pm UTC](https://community.n8n.io/t/sub-workflow-error-missing-node-to-start-execution-please-make-sure-the-workflow-youre-calling-contains-an-execute-workflow-trigger-node/209351/4 "2025-10-21T17:11:17Z")

</div>

🙂 glad that I could help you!

Maybe node versions with the new version update conflict I guess 🤷…

Mark the answer as solved , if it helped.

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\
**Post date:** [October 28, 2025, 5:11pm UTC](https://community.n8n.io/t/sub-workflow-error-missing-node-to-start-execution-please-make-sure-the-workflow-youre-calling-contains-an-execute-workflow-trigger-node/209351/5 "2025-10-28T17:11:52Z")

</div>

Closed on October 28, 2025, 5:11pm UTC

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