All of my google sheet triggers have stopped working

Get Help
1

Hi there,

I have two gumloop flows based on a trigger from google sheets. They both stopped working today. Can you help me understand why?

Here’s one: https://www.gumloop.com/pipeline?workbook_id=iVdnuqdG8oScYMUupZ9wzC
Here’s the google sheet it works out of: Compound Check-ins - Google Sheets

Here’s the other: https://www.gumloop.com/pipeline?workbook_id=nKQr8C8jaT2DGYCa4vffwf
Here’s the google sheet it works out of: Compound Code Responses - Google Sheets

Any help appreciated?! Have deleted and re-added the node and the sheet several times.

2

Hey @hallixrap! 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.

  1. Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}}

  2. Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
    GIF guide

  3. Provide details about the issue—more context helps us troubleshoot faster.

You can find your run history here: https://www.gumloop.com/history

3

Hey @hallixrap –

Thanks for flagging this. I checked both workbooks and all recent runs appear to have been successful. Generally, a trigger gets disabled only if a flow encounters three consecutive errors, as a precautionary measure. When that happens, the user is notified via email. I don’t think that’s the case here, and it doesn’t seem like the trigger was disabled.

It sounds like you’re referring to certain rows not being picked up by the trigger, is that right? If so, is there anything specific about this data compared to the others? Also, could you confirm if the trigger has been working as expected since?

4

Hi @Wasay-Gumloop - it all started working last night for some reason and I’m a bit worried about the fragility of this and I didn’t get a notification saying the trigger had been disabled.

Certain rows were just not picked up last night on both of my flows after around 15.45 British Summer Time.

Is there any explanation for what that could have been? Trigger worked again on testing yesterday. I’ll test again today.

5

Got it. I don’t think the trigger being disabled was the issue here, but I wanted to flag it just in case. If the trigger was actually disabled, the node wouldn’t have picked up the new rows at all.

There are a few edge cases I wanted to highlight:

  • Inserting Columns: The system adapts if columns are inserted between existing ones, but it may trigger for any rows where the row hash changes.
  • Deleting Columns: Same thing here – the system will adapt, but could trigger for any rows where the row hash changes.
  • Row Deletions (Create mode): No trigger occurs when rows are deleted.
  • Row Reordering (Create mode): Not detected.

How has the trigger performed today? One other suspicion is a 500 error from Google, but that’s probably unlikely. We’re planning to add more logging soon so we can catch any such edge-cases. Still, it’s a bit tricky to get to the root cause since we don’t have full access to the sheet or all the context around what changed.

6

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.