n8n - 💡(How to fix) Fix URGENT - Wait node "Invalid token" error blocking production workflows after 2.16.1 update [1 comments, 2 participants]

Describe the problem/error/question

After the automatic update to version 2.16.1, all Wait nodes are returning "Invalid token" error when calling resumeUrl. This completely blocks production workflows that use the Wait node with resume:webhook option.

What is the error message (if any)?

{"error":"Invalid token"} This error appears when clicking buttons in emails sent by Wait node, or when calling resumeUrl directly via POST request.

TL;DR

Downgrade to a version prior to 2.16.1 or wait for a future version that fixes the "Invalid token" error in Wait nodes.

Guidance

• The issue is likely caused by a bug introduced in version 2.16.1, as confirmed by multiple users in the community forum.
• To verify the issue, try creating a new workflow with a Wait node and resume:webhook option, and check if the "Invalid token" error occurs when calling resumeUrl.
• As a temporary workaround, consider downgrading to a version prior to 2.16.1, if possible, to restore functionality to existing production workflows.
• Monitor the community forum and release notes for updates on a future version that fixes this issue.

Notes

The provided information does not include enough details to suggest a code-level fix, and the issue appears to be a known bug affecting multiple users.

Recommendation

Apply workaround: Downgrade to a version prior to 2.16.1, as this is the only known solution that can immediately restore functionality to affected workflows, despite the potential drawbacks of using an older version.