Skip to main content

Hello everyone, 

I'm running more than 10 zaps with Google Sheets integrations and the step “Find Spreadsheet Row in Google Sheets” sometimes gives an error “Error 502 (Server Error)!!1”. The 1 is not a typo. It started happening about a month ago in all my 10 zaps. I don't see a pattern when it does/doesn't happen. 

Does anyone know how to fix this, or have ideas of what I could try?

Best,

Caspar

Hi @CasparSmits 

Help links for using GSheets in Zaps: https://zapier.com/apps/google-sheets/help

Check your Zap app connection here: https://zapier.com/app/connections

 

 


Hi @CasparSmits,

​This type of "Internal Server Error" (500) error can happen from time to time when a server is under heavy load, or if the data trying to be passed is too large or for a whole variety of other circumstances. 

Since this happens on the other app's end we can't see exactly what might be the specific problem here, but the good news is that these issues are usually short-lived. Generally, once they settle back down, failed tasks can be replayed in bulk from the Task History.

To find more info on replaying tasks, I'd recommend this help doc: https://help.zapier.com/hc/en-us/articles/8496241726989-Replay-Zap-runs

Hopefully, this helps.


Hi @ken.a,

Thank you for your reply. What do you mean with settle back down? It doesn't seem it's going to stop by itself, it happened 16 times, and it started 7 weeks ago. Twice in july, 4x in August and so far, 10x in September. 

Could it have to do with the size of the Google Sheet? I think I will try to split up the different worksheets into separate sheets.

Best,

Caspar


Hi @CasparSmits,

 

It's a great idea to split up the size of your Google Sheets files so uploading them will be manageable. "Internal Server Error 500" usually means that Google's server is overloaded. Let us know if that occurs again after you split most of your worksheets. Thank you.


I am having the same issue here. It is happening multiple times a day. It first started a few months ago. It did settle down, however it is now worse than ever before. I have had 9x errors in the last 24 hours with the cause “the app returned “error 502 (server error)!!1” Even when replaying the error I am sometimes getting the same error. 


Hi @buttonedup,

Based on the details you've provided, one possible solution could be to refresh your Google Sheets connection. Here's how you can do that:

  1. Go to your My Apps page here: https://zapier.com/app/connections/google-sheets
  2. Click the 3 dots to the right of your connection
  3. Click Reconnect.
  4. When prompted, log in to your Google account and select the needed permissions. 

Kindly give it a try and let me know how it goes? I'll keep an eye out for your response!


I’m having the same issue. Tried the above and did not work. 

However the error changed from the one originally posted to “Error message: This usually happens when the Zap does not receive a response from Google Sheets within 30 seconds confirming we could access the spreadsheet data successfully.”

 

 


Hello,

I landed on this topic while looking for reasons that would explain the load of 502 error codes I’m getting these last days when using the Google API (with their nodeJS client).

I guess that it’s related to Google servers and not really an issue with Zapier? (since I also get them when calling their API almost directly)

 

I hope this helps.
Best regards.
William


Hi @Steve_M and @VeeForm,

It looks like we're timing out when attempting to gather or send information from the app. 

When Zapier makes a request, we wait almost exactly 30 seconds for a response. If the app takes longer than 30 seconds to respond, we call it a "timeout" -- which is considered an error. Basically, we didn't hear back from this app in time to know whether or not our request was successful. 

Some more info and possible solutions can be found here: https://zapier.com/help/troubleshoot/errors/fix-timeout-errors-in-zaps

These errors are usually from the source app and not with Zapier. However, if you keep encountering this issue I would recommend reaching out to our Support Team to have them take a closer look at this issue since they have the correct tools to look closer at the Zap and its logs. You can contact our Support Team here: https://zapier.com/app/get-help

Hopefully, this helps.


I am also having this issue the last two days (since 24th Sept 2024). I’ve tried to reconnect the connection to Google Sheets, if there are any other things to try, please let me know. Thanks 


Hi @Rob Flux,

Unfortunately, I have exhausted my resources regarding this issue. I recommend reaching out to our Support Team to investigate this issue further since our Support Team has the correct tools to look closer at the Zap and its logs.

You can reach our Support Team here: https://zapier.com/app/get-help

I appreciate your patience and understanding.


I’ve tried to use the above link but am going around in circles with gettng help. What’s the email address for support please?


Hi! I have the exact same issue, been having it for the last few days. Will submit a ticket to Support Service


Hi @Rob Flux,

You have to contact our Support Team via our Contact Form. You can choose the “Report a bug or request a feature” button. Like so:

63b609b42a669744e00049942cea538e.png
(view larger)

Hopefully, this helps.


Hi guys, I’m facing the same issue on Power BI with scheduled updates that use google sheets…

It’s started at the last tuesday (24). Is that an issue with google servers…? do you have any news about that?


 

We have the same problem that started appearing a few days ago and keeps recurring. Looking at the reports, it's a global problem.


It’s been getting really bad for me over the past week @ken.a I think you need to escalate this accordingly on your end. This sounds like something that Zapier will need to escalate or work with Google support on. Too many users have this issue at the same time. 

I’m running into issue where I can no longer make changes and publish updates to workflows. You can use this one as an example https://zapier.com/editor/243553555. (this has about 15-20 steps where the same sheet might be used (but generally only uses the sheet action about 5 times) but it can’t get past the first row look up and this is the 2nd step of the zap then it fails. Sometime a re run will work and sometime it doesn’t. 

I’m currently testing moving the call to the Google sheet to a sub zap. It worked for another workflow...at least now I can make updates to that workflow.


Like look at this. 

Even when trying the sub zap. 1 step. 1 sheet can it can’t find the look up column. Also doing this in Firefox incognito mode so no browser cache issue. 
 

 


Hi ken.a, I don’t have the options you have screenshot above to ‘report a bug’. Here is what I see below. I’ve gone ahead and said ‘something else’ but want to ensure this gets correctly escalated please.

 

 


this is happening to me for the last couple weeks and i still haven’t able to mitigate this. Is there something has to be done by either Google/Zapier?


I also have a Zapier that started failing on Sept. 24th 8.31am UK Time. Curiously the exact same day then reported by @Rob Flux.


Hello, I have the same issue on almost all my Zaps.

I have more than 20 Zaps and these have been working perfectly well for over a year.

Recently this error with “The app returned "Error 502 (Server Error)!!1".” started occurring.

It’s a real pain point, I have to re-start most of my 20 Zaps manually multiple times a day now.

=> Does the Zapier team have a plan for a fix, or automated retries when that happens?


https://community.make.com/t/error-in-google-sheets-module-cant-understand-the-issue/56086/4

Hi everyone, based on the comment of TFisch in this link above, the dev team of google is working to fix this issue


I am getting the same errors from a single small sheet (7 rows and 3 columns) that worked for years and is getting worse every day.


Hi friends,

I have added you all to the open bug report for the 502 error in the Google Sheets integration. While we can’t provide an exact ETA of the bug’s fix. We will keep you updated once the bug is fixed.

I appreciate your patience and understanding.


Reply