n8n - 💡(How to fix) Fix Respond to Webhook hangs indefinitely when workflow has multiple triggers connected to the same downstream flow [2 comments, 3 participants]

Bug Description

Bug description

Respond to Webhook hangs indefinitely when the workflow contains more than one trigger connected to a shared downstream normalization/routing section.

I have a workflow with multiple ingress triggers:

• Webhook
• When chat message received
• WhatsApp Trigger

All of them connect into a shared normalization/routing section of the workflow. However, only the execution path that starts from the Webhook trigger is intended to reach the Respond to Webhook node. The other triggers have their own downstream handling and are not intended to respond through Respond to Webhook.

The Webhook node is configured with:

• Respond: Using Respond to Webhook Node

This workflow was working correctly in previous n8n versions with the same multi-trigger structure. The issue started appearing after upgrading n8n. I am currently running n8n 2.19.0.

When only the Webhook trigger path is connected, the workflow works correctly and the Respond to Webhook node returns the response.

However, as soon as I connect any additional trigger to the same shared normalization/routing section, for example When chat message received or WhatsApp Trigger, webhook executions remain stuck in Waiting forever and never return a response.

This happens even when the execution is started by the Webhook trigger and follows the expected Webhook-only branch toward Respond to Webhook.

I confirmed that the response body is not the issue: I tested a simple Edit Fields node returning { "test": "ok" } immediately before Respond to Webhook, and it works when the webhook trigger is the only connected ingress. The issue only appears when another trigger is connected to the shared part of the workflow.

This seems similar to a previously reported issue: “The Respond to Webhook node hangs if the workflow has two triggers”.

Note: issue is also present in beta and stable version

To Reproduce

To reproduce

1. Create a workflow with a Webhook trigger.

2. Set the Webhook node’s Respond option to Using Respond to Webhook Node.

3. Connect the Webhook node to a simple node, for example Edit Fields, that outputs:

   {
     "test": "ok"
   }

4. Connect that node to Respond to Webhook.

5. Execute the workflow and send a POST request to the webhook test URL.

6. Confirm that the webhook responds successfully.

7. Add a second trigger to the same workflow, for example: When chat message received, or another trigger such as a WhatsApp trigger.

8. Connect this second trigger to the same downstream node/path used by the webhook flow.

9. Execute the workflow again from the Webhook trigger by sending a POST request.

10. Observe that the execution stays in Waiting and the Respond to Webhook node never returns a response.

Expected behavior

Expected behavior

### Expected behavior

If the execution is started by the `Webhook` trigger, `Respond to Webhook` should return the response normally, even if the workflow contains other triggers that are connected to the same downstream flow.

The presence of other triggers should not prevent a webhook-triggered execution from being associated with its pending webhook response.

### Regression note

This same workflow structure was working correctly in previous n8n versions.

The problem started after upgrading n8n. I do not know the exact previous version where it last worked, but the current affected version is:

- n8n version: `2.19.0`

Because the workflow previously worked and now hangs with the same structure, this may be a regression related to `Respond to Webhook` and workflows with multiple triggers.

### Debug Info

I am using n8n Cloud, so I do not have direct access to the underlying Node.js version or database details.

Environment shown in the UI:

- n8n version: `2.19.1`
- Hosting: `n8n cloud`
- Execution mode: `main (default)`
- Operating system: `n8n Cloud`
- Node.js version: `Unknown - n8n Cloud`
- Database: `Unknown - n8n Cloud`

Instance ID shown in About n8n:

`027e1de9a1f2bc3e4bb335e9cef8f5e9392f3a0289408b83742436a732c877a7`



### Operating System

n8n Cloud

### n8n Version

2.19.0

### Node.js Version

Unknown - n8n Cloud

### Database

SQLite (default)

### Execution mode

main (default)

### Hosting

n8n cloud