Getting failed runs from a Google Sheets Reader Node in the middle of a flow. Has happened a few times now. I re-auth’ed all google accounts and then manually run the flow and it ends up working. But that’s obviously annoying. So, what can I do to make sure it runs smooth on auto-pilot?
Hey @gummydummy! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.
-
Find your run link on the history page. Format:
https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}} -
Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
-
Provide details about the issue—more context helps us troubleshoot faster.
You can find your run history here: https://www.gumloop.com/history
Here’s the run link: https://www.gumloop.com/pipeline?workbook_id=5T7TUZLQtbkkXiMqehMnxG&run_id=T642r9dxyAcmCd2QSkKfog
Hey @gummydummy – Thank you for sharing the run link. From what I can see, all the sheet reader nodes in that run actually did execute successfully. I’m not sure exactly where the node failed. If you’re able to share any screenshots or provide more details, that would be really helpful. Also, was this just a one-off issue, or have you been seeing this happen consistently?
Thanks for the reply. It’s still happening a few times a day. Here is the most recent run error from 3 mins ago:
After receiving this error, I just went into the flow and clicked “Run” and it works no problem.
oh I see – this was essentially a 500 error from Google, which means the service was temporarily unavailable on their end. These error resolve themselves shortly after, which is why it worked when you retried. You should be all set now.
<HttpError 503 when requesting https://sheets.googleapis.com/v4/spreadsheets/14V3wotq9LRDTHFlcof6NUrUBQQTtAXWMd_RkFo6NuhU/values/Sheet1%21A1%3AZZ10000000?alt=json returned "The service is currently unavailable.". Details: "The service is currently unavailable.">
Okay. And if a run fails for this reason, will the next run continue as normal? And is there any way to re-run failed runs in the same way that Zapier allows you to re-run a failed zap attempt with the same data?
Yes the next run should continue normally. There’s also a Resume option to re-run flows from any of the last saved point:
Hi Wassay, where do I find this “resume” option? I don’t see it in my flow.
Hey @gummydummy – Its available on the run link, not on the workflow link. You can find run links from the Previous Runs Tab:
I’m not seeing this. I go into the error from the email I receive, I then click previous runs, I then look around and do not see “Resume” anywhere. Do I need a different account/level/access to use this?
Hey @gummydummy, yes, you can access this across all accounts.
Here’s the run link you previously shared for example: https://www.gumloop.com/pipeline?workbook_id=5T7TUZLQtbkkXiMqehMnxG&run_id=T642r9dxyAcmCd2QSkKfog
If you open that link, you should see the option to resume the run (since it stopped mid-flow). Same applies for any other flow — if it’s stopped midway for any reason, you can pick it up again from the node it paused on.
To check on previous runs, just open the relevant workbook and go to the “Previous Runs” tab. That’ll list all the flows you’ve executed for that workflow. You can click into any of them to dig deeper — and if a run is paused, you’ll be able to resume it from there too.
So here’s what happens…
I follow your instructions:
Click previous runs, select a failed run, then this loads where I say “Resume”
But within seconds the resume disappears and I see this:
And this:
So, I go through the process again (clicking into the failed run from previous runs) and quickly click “Resume” before the button disappears and the run still fails.
Any suggestions or solutions for this?
For context, this run failed 4 times in the last 24 hours.