-
Notifications
You must be signed in to change notification settings - Fork 9.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
Problem with gmail and http request nodes in version 0.139.1. #2256
Comments
Please try again with the just released [email protected] It contains multiple fixes |
On [email protected] and [email protected] same problem with Gmail node. |
Thanks for confirming. Did assing to @krynble he will have a look. |
Hello @Yaccobv2 Thanks for your report. I was able to reproduce and fix the Gmail issue. You can find the PR #2289. Should be released soon. On a side node, I tested the HTTP Request issue you mentioned and was unable to simulate. One thing to node is that the I have created a sample node that you can use here:
|
As @krynble mentioned did the issue get fixed and is now also merged. Will be released with the next version. |
Fix got released with [email protected] |
Hi! There is a problem with gmail node and http request node in version 0.139.1. After I restored n8n to version 0.138.0 everything works perfectly fine.
Gmail node does not apply selected tags and queries correctly, for example node reads emials without "UNREAD" tags or emails that doesn't contain query text "test emails". Also the last item returned by this node is undefined and it repeats itself every time I run the workflow.
Configuration:
Http request doesn't send binary files and results with error:
"Converting circular structure to JSON --> starting at object with constructor TLSSocket | property _httpMessage -> object with constructor ClientRequest --- property socket closes the circle"
Configuration:
Hope you are able to solve this issue or guide me how should I resolve it in my workflow :) (CC @dolohow)
The text was updated successfully, but these errors were encountered: