-
Notifications
You must be signed in to change notification settings - Fork 8.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Webhook Error with 0.221.0 #5765
Comments
Thanks for the report @luizeof and @tiagocordeiro we will get this sorted. Unrelated to this are you both running something like watchtower or was the upgrade done manually? |
Here the same, almost every execution is marked as "Failed". I have to open one by one to see if it's true or not |
Hi All, Not sure if this is related but we're also getting "Problem running workflow -- require(...).Webhook is not a constructor" for all webhook connectors. 0.220.0. If it is unrelated, we will create a new issue. Edit - Fixed in the 0.220.1 latest release |
@devanshkaloti that sounds like a different problem. Can you please open a new issue, and add more details, including a stacktrace (if possible). 🙏🏽 |
@luizeof @tiagocordeiro Thanks for reporting this. If this image fixes the issue, we'll create a new release |
Issue got also reported in the forum: |
I can reproduce this issue on my end as well. |
@MeesJ did you update the main server, the worker, and the webhook server? |
I don't know what you mean exactly. I'm running n8n in a single instance, which is now running on the |
@MeesJ in that case the issue you are facing is something else. This issue only exists in the separate webhook server running in the queue mode. Can you please open a new issue with stacktrace of the error you are seeing? |
@goulahyane @luizeof @tiagocordeiro Can you please try to upgrade to |
@netroy it works! |
Hey @netroy, just tested the latest pushed image, seems to be solving the issue. |
Fix got released with |
Describe the bug
All requests arriving at the Webhook node are generating an error, but no log, no data. Simply the workflow is marked with error without any information.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: