Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix Webhook upgrades to versions 2.16.0 and 2.17.0 have serious bugs and require urgent attention. [4 comments, 3 participants]

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…
GitHub stats
n8n-io/n8n#28462•Fetched 2026-04-15 06:44:25
View on GitHub
Comments
4
Participants
3
Timeline
12
Reactions
1
Author
luka-mimiluka-mimi
Participants
groundbreakersonlinegroundbreakersonlineluka-mimiluka-mimin8n-assistant[bot]n8n-assistant[bot]
Assignees
shortstackedshortstacked
Timeline (top)
commented ×4labeled ×3subscribed ×3assigned ×1

Error Message

  • error: all

Code Example

{
  "nodes": [
    {
      "parameters": {
        "httpMethod": "POST",
        "path": "668c45eb-c43b-49c6-9fc6-d781633a0356",
        "responseMode": "responseNode",
        "options": {}
      },
      "type": "n8n-nodes-base.webhook",
      "typeVersion": 2.1,
      "position": [
        608,
        96
      ],
      "id": "da49e4e4-adf7-4308-b760-012864cf1ef8",
      "name": "Webhook",
      "webhookId": "668c45eb-c43b-49c6-9fc6-d781633a0356"
    },
    {
      "parameters": {},
      "type": "n8n-nodes-base.wait",
      "typeVersion": 1.1,
      "position": [
        832,
        96
      ],
      "id": "77b460a1-dec9-4d96-91ca-acaca4524cff",
      "name": "Wait",
      "webhookId": "5ef4bc16-4318-4c5e-b337-8eb41b4cb536"
    },
    {
      "parameters": {
        "respondWith": "json",
        "options": {}
      },
      "type": "n8n-nodes-base.respondToWebhook",
      "typeVersion": 1.5,
      "position": [
        1040,
        96
      ],
      "id": "1992c91d-9c56-4ff7-ac9c-091f69b980ce",
      "name": "Respond to Webhook"
    }
  ],
  "connections": {
    "Webhook": {
      "main": [
        [
          {
            "node": "Wait",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Wait": {
      "main": [
        [
          {
            "node": "Respond to Webhook",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "pinData": {},
  "meta": {
    "instanceId": "833c78570fd4b31c71e8110775458cd1bc18942f348fe7a25e3967cc5c79ec53"
  }
}
RAW_BUFFERClick to expand / collapse

Bug Description

If a webhook contains a wait node, it may cause the webhook to become unresponsive.

Operational environment: Google GCP Kubernetes 3 main servers 15 workers 1 webhook

I feel my enterprise-level payment wasn't properly guaranteed, and I haven't received a response after contacting customer support via email.

The testing workflow is as follows:

{
  "nodes": [
    {
      "parameters": {
        "httpMethod": "POST",
        "path": "668c45eb-c43b-49c6-9fc6-d781633a0356",
        "responseMode": "responseNode",
        "options": {}
      },
      "type": "n8n-nodes-base.webhook",
      "typeVersion": 2.1,
      "position": [
        608,
        96
      ],
      "id": "da49e4e4-adf7-4308-b760-012864cf1ef8",
      "name": "Webhook",
      "webhookId": "668c45eb-c43b-49c6-9fc6-d781633a0356"
    },
    {
      "parameters": {},
      "type": "n8n-nodes-base.wait",
      "typeVersion": 1.1,
      "position": [
        832,
        96
      ],
      "id": "77b460a1-dec9-4d96-91ca-acaca4524cff",
      "name": "Wait",
      "webhookId": "5ef4bc16-4318-4c5e-b337-8eb41b4cb536"
    },
    {
      "parameters": {
        "respondWith": "json",
        "options": {}
      },
      "type": "n8n-nodes-base.respondToWebhook",
      "typeVersion": 1.5,
      "position": [
        1040,
        96
      ],
      "id": "1992c91d-9c56-4ff7-ac9c-091f69b980ce",
      "name": "Respond to Webhook"
    }
  ],
  "connections": {
    "Webhook": {
      "main": [
        [
          {
            "node": "Wait",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Wait": {
      "main": [
        [
          {
            "node": "Respond to Webhook",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "pinData": {},
  "meta": {
    "instanceId": "833c78570fd4b31c71e8110775458cd1bc18942f348fe7a25e3967cc5c79ec53"
  }
}

To Reproduce

  1. Create a new webhook POST trigger

  2. Change the Respond node to Using 'Respond to Webhook'

  3. Add a wait node

  4. Add Respond to Webhook

  5. Test with API testing tools; no effect observed during the call.

Expected behavior

It can respond normally

Debug Info

Debug info

core

  • n8nVersion: 2.16.0
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: postgres
  • executionMode: scaling (multi-main)
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: 91dd5fce-af6b-400a-b1ab-cb3ab247178b

storage

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

pruning

  • enabled: true
  • maxAge: 4000 hours
  • maxCount: 100000 executions

client

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

security

  • secureCookie: false

Generated at: 2026-04-14T10:29:48.689Z

Operating System

Docker

n8n Version

2.16.0,2.17.0

Node.js Version

24.14.1

Database

PostgreSQL

Execution mode

queue

Hosting

self hosted

extent analysis

TL;DR

The webhook may become unresponsive due to the wait node, and a potential fix is to review the workflow configuration and adjust the wait node's parameters or remove it if unnecessary.

Guidance

  • Review the workflow configuration to ensure the wait node is properly configured and necessary for the workflow.
  • Check the Respond to Webhook node's configuration to ensure it is set up to respond correctly after the wait node.
  • Test the workflow without the wait node to see if it responds normally.
  • Consider adjusting the execution mode or concurrency settings to improve performance.

Example

No code snippet is provided as the issue is related to workflow configuration.

Notes

The issue may be specific to the n8n version (2.16.0) or the Docker environment, and further investigation may be needed to determine the root cause.

Recommendation

Apply workaround: Review and adjust the workflow configuration to ensure the wait node is properly configured and necessary for the workflow, as this is the most likely cause of the issue.

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

It can respond normally

#api#model save/load#optimization#mixed precision#training loop

Still need to ship something?

×6

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

Back to top recommendations

TRENDING