I’m experiencing an issue with a scenario that keeps throwing an error in the Google Sheets module, causing it to break. I can’t pinpoint the reason for the error. When I manually re-run the scenario once or twice, it works without issue.
The error message is quite lengthy, but I’ve attached a portion of it along with an image for reference.
"Error
Error 502 (Server Error)!!1 *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-........."
Same here. Make support has confirmed that their dev team is aware of this issue and the issue is on Google’s side. I’d recommend turning on “Store incomplete executions” and use Break error handlers until they’ve resolved it. (I’d recommend those 2 things with Google modules in general though.)
They have claimed the google drive issue is fixed, which it is, but this issue is still an ongoing problem. I have implemented work arounds in my scenario. Wiating for update from make. also same problem happening at zapier:
Ever since google added new subprocessors this week…yeeesh! I don’t know if its related, but my Chrome has had weird pixel issues, this google api is cuasing havoc, and google is just slow in general. too big for its own good, house of cards LOL
Hi guys! I’m facing the same issue in power bi service when it tries to update data from google sheets!
I’m facing it since the last tuesday (24)…do you have news about that?
One of my clients has gotten HUNDREDS OF GOOGLE SHEETS ERRORS just like this over the last 2-3 weeks. This is driving my client insane. Make, please fix your relationship with Google so they do not block you like this!
Has anybody else opened up a support ticket with Make about this? All of my clients have opened up support tickets with Make, but Make Tech Support is refusing to admit that there is a problem.
We apologize for all the trouble this issue has caused.
Our developers are aware of this issue and detected that it originated from Google. This issue is currently still under investigation and we are actively searching for a solution.
We will update you as soon as possible. Thank you for understanding.
The issue you are experiencing is related to an error with a Google service, which, unfortunately, is beyond our control.
However, we’ve implemented a solution to handle this by treating the error as a ConnectionError. This approach allows the scenario to automatically retry in case of a 502 error.
Thank you, is there a way to track the issue through google, do they have a service page specific to this? Do you know if they are planning to provide further resolution or is this the new normal?
