Gmail-Reader Failing As Trigger!

Get Help
1

Hey guys, I have Gmail Reader set up as a trigger for a flow. Two important details: (1) It runs perfectly when I manually click “Run” and (2) It was running perfectly as a trigger until 2 days ago when it stopped. I’ve worked through all of Gummie’s suggestions (reauth the credentials various settings on Gmail Reader etc) and still getting zero triggers. Any suggestions/help would be really appreciated.

2

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.

  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

btw worth mentioning I’m not getting any errors because the trigger isn’t firing… and like I said when I manually run the flow, it works perfect.

4

I’m guessing the team will need this in order to comment?

https://www.gumloop.com/pipeline?run_id=ZcFoFKTUc8VCoyhpbtcuMj&workbook_id=5T7TUZLQtbkkXiMqehMnxG

5

Hey @gummydummy, could you please try the following:

  1. Disable the trigger from the workflow
  2. Save the workbook. At this point, you’ll notice that the trigger notice on the top of the workflow would disappear
  3. Delete the Gmail reader node and add it back from the node library
  4. Connect it with the nodes and enable the trigger
  5. Select the label from the label drop-down and not by enabling it as a dynamic input and then typing in the label

Let me know if that makes sense and works for you. You can do a test by add an email to that label and checking previous runs for a triggered execution:

image
image744×454 18.4 KB

6

Hi @Wasay-Gumloop - thanks for following up. So, I haven’t changed anything and the flow started working again yesterday morning. It had been down for 48-36 hours. I did make changes at the time it went down (e.g. re-authenticated Gmail) but nothing else.

Before I start building flows to support my business, can you please let me know if this is the sort of thing I should be expecting? Meaning should I expect unexplained downtime like this for flows… or any downtime like this for that matter?

Thanks again for your help.

7

Hey there! This is definitely not expected, and I’m going to investigate why that happened. Couple questions that could help narrow this down:

  1. Were the emails manually moved into the label or were they automatically assigned in that label?
  2. Do you have more than one workflows with an active Gmail trigger for the same Gmail account?
8

Thanks for following up.

So, the label is automatically applied every time a particular email type (e.g. application) is received.

I did have a second workflow setup with a Gmail Reader trigger but I turned this off probably 12-24 hours after I noticed the second workflow stopped working.

Is it not possible to have a second Gmail Reader trigger in a separate (not sub) flow?

Thanks!

9

Hey @gummydummy – Yes, Gmail can have issues when more than account has a event based-trigger. There are some more details here and a recommend solution using Time Trigger if you want to explore that and have multiple triggers: Gmail Reader - Gumloop

That said, we’re also going to move from Google watch response API to our own solution to avoid this in the near future.

If you only have one trigger / account then you should be all set!

10

Hi @Wasay-Gumloop thanks for letting me know - I would ideally like to have a second flow using a gmail reader trigger so hopefully that gets resolved soon. For now, I’ll leave the single flow operating with the gmail reader trigger and wait for the update.

11

Sounds good! Let me know if you run into anything else :slight_smile: