Hundreds of Google Sheets errors!

There is a major problem happening with Make and Google Sheets, and Make Support has so far refused to admit that there is a problem.

Starting approximately 2-3 weeks ago, all of my clients who have Google Sheets scenarios are receiving hundreds of Google Sheets “502” errors.

We are doing nothing wrong in our scenarios. The scenarios have been working perfectly fine for years.

Then suddenly, as of approximately 2-3 weeks ago, the Google Sheets modules are constantly giving us error messages. This is typically happening on the “Add A Row” modules.

We we are not sending the data to Google Sheets too quickly — we have sleep modules to make sure that things are being sent nice & slow to Google Sheets. We also have the highest paid Google Sheets Enterprise account that you can pay for with Google.

Every single time we run the scenario, we get error messages from Google that you can see in the screenshot below.

Even if we try to manually re-run the scenario, we get an error message.

We have done nothing wrong in our scenario, but Google Sheets has apparently blocked Make, because Google Sheets is giving us constant error messages.

It is happening to every Google Sheets module in our scenarios, and it is happening in every Google Sheets scenario that my clients have.

Make, we need you to please fix this problem ASAP!

Thank you!

2 Likes

same error here! Has been happening for nearly a week now.

Hi Scott,

On first glance, that screenshot you have sent does not typically appear to be a message you would get from a module output in Make. Where did you screenshot it from?

The error from Make was a gigantic scrolling block of HTML code that is unreadable. So I rendered the HTML in a web browser to be human-readable.

Here’s what the raw error from Make looks like, before I rendered the HTML in a web browser to be human-readable.

This is happening to all of my clients who are using Google Sheets.

Frustratingly, Make Support still refuses to admit that there is a problem.

Same here. Do you notice any pattern in time of day? I am adjusting to see if that makes a difference. Regardless, if I run the scenarios manually, they work fine. @Make_Bot please advise

Hey @here

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. :pray:

1 Like

Can’t comment to the specific issue as my Google sheet scenarios are working fine, but a client of mine who uses Zapier was having a whole bunch of Google Sheet errors in the last week or two.

Got them to reconnect their connection and haven’t seen those errors since. Have you tried doing something similar in your case?

1 Like

Thanks, @D-EFFCON! We just tried this and unfortunately, it didn’t solve the issue. :frowning:

I would love an update on this as well as this has been happening for me notably since Sept 23rd. I have had to implement breaks, and retries in my 50+ sheets modules just so my clients can keep things “afloat” and I am manually monitoring the others to make corrections as needed, its exhausting.

1 Like

Hello @here

I’m bearing an update for you!

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 for your support and understanding :pray:

Excellent response and can confirm this worked for me on last nights executions.

It works, but it is causing more make tasks to be used up on retries. I have hundreads of hits on this every day with my apps. Would be great if the Great Google would let us know whats actually wrong so we can make some decisions.

Also to add further, my scenarios are having constant 502 errors with google sheets, I don’t think anything has been really “fixed”

There is a more indepth google side issue tracker here:

https://issuetracker.google.com/issues/369670473?pli=1

1 Like