n8n - 💡(How to fix) Fix webhook-waiting resumeUrl returning 'Invalid token' — possible regression (ref: GitHub #18610) [2 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#28995Fetched 2026-04-24 06:12:52
View on GitHub
Comments
2
Participants
3
Timeline
5
Reactions
0
Timeline (top)
commented ×2labeled ×1mentioned ×1subscribed ×1

Error Message

I'm experiencing an issue on my n8n Cloud instance where clicking a button that triggers a webhook-waiting resume URL returns {"error":"Invalid token"}.

Describe the problem/error/question

What is the error message (if any)?

  • When the user clicks the button, the browser opens the resume URL and n8n returns {"error":"Invalid token"}
  • error: all

Fix Action

Fix / Workaround

Could you please check:

  1. Whether my instance received an update between yesterday and today
  2. Whether this is a known regression in v2.17.5
  3. Any recommended workaround or fix

Code Example

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Hi n8n support team,

I'm experiencing an issue on my n8n Cloud instance where clicking a button that triggers a webhook-waiting resume URL returns {"error":"Invalid token"}.

Instance: https://recharge-marketing.app.n8n.cloud n8n Version: 2.17.5 Workflow ID: Sg9l7ZWxo7Mgb0us (now renamed to 'Prod - AI - CRM - Campaign Content Generator GDrive & Slack + Memory')

Describe the problem/error/question

  • My workflow uses Wait nodes (resume: webhook) to pause execution until a user clicks a button in Slack
  • The Slack message contains a link button with the $execution.resumeUrl as the URL

What is the error message (if any)?

  • When the user clicks the button, the browser opens the resume URL and n8n returns {"error":"Invalid token"}
  • The execution is still in a 'Waiting' state when the button is clicked

What changed:

  • This was working correctly yesterday (22 April)
  • It stopped working today (23 April) without any changes to the workflow or credentials
  • All other parts of the workflow (Slack posting, Google Docs creation, Gemini API calls) continue to work fine
  • Only the webhook-waiting resume URL is affected

This appears to match the behaviour described in GitHub issue #18610 (sendAndWait broken with missing/invalid token), where webhook-waiting URLs return 'Invalid token' after a platform update.

Could you please check:

  1. Whether my instance received an update between yesterday and today
  2. Whether this is a known regression in v2.17.5
  3. Any recommended workaround or fix

Happy to provide execution IDs or additional details if needed.

Thanks, Santiago

Please share your workflow/screenshots/recording

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

Share the output returned by the last node

<!-- If you need help with data transformations, please also share your expected output. -->

Debug info

core

  • n8nVersion: 2.17.5
  • platform: docker (cloud)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 20
  • license: enterprise (sandbox)

storage

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

pruning

  • enabled: true
  • maxAge: 720 hours
  • maxCount: 25000 executions

client

  • userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-04-23T13:28:24.612Z

extent analysis

TL;DR

The issue is likely due to a regression in n8n version 2.17.5, causing webhook-waiting resume URLs to return "Invalid token", and a workaround or fix may be available.

Guidance

  • Check if the instance received an update between April 22 and 23, which may have introduced the regression.
  • Verify if this is a known issue in version 2.17.5 by checking the GitHub issue #18610.
  • Consider reaching out to the n8n support team for a recommended workaround or fix, as they may have more information on the regression and potential solutions.
  • Provide execution IDs or additional details to the support team to help them investigate the issue further.

Notes

The issue seems to be specific to the webhook-waiting resume URL, and other parts of the workflow are working fine. The fact that it was working correctly yesterday and stopped working today without any changes to the workflow or credentials suggests that an external factor, such as a platform update, may be the cause.

Recommendation

Apply workaround: The user should wait for a response from the n8n support team regarding a potential workaround or fix, as they may have more information on the regression and potential solutions.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING