Gmail trigger not firing
The Gmail trigger is very temperamental but today it isn't firing at all when a new email lands, is this a symptom of yesterday's GCP outage? How can I get better reliability from this trigger?
11 Replies
Hi @Chris Wright | Because You Can Could you please delete and re-add the trigger and then deploy? I just now tested and it is working. Let me know if you still face issues after it.
Processing...
🤖 Gathering bytes and bits. 🧲 this might take a couple of minutes... beep boop
🤖 AI Response
Redeploying triggers is a recognized troubleshooting step for resolving functionality issues in BuildShip workflows. The recommended process involves deleting the current trigger node, re-adding it with the same configuration, and then redeploying (shipping) the workflow. This refreshes the trigger connection and has been confirmed to resolve similar issues for other users. Additionally, it is important to ensure that the workflow containing the trigger is shipped before testing it with an Execute Workflow node, as unshipped workflows can cause triggers to be unresponsive. If problems persist after these steps, further investigation into configuration or data formatting may be necessary.
🔗 References:
1. https://support.buildship.com/m/1248609614707036191
2. https://support.buildship.com/m/1265724954825982044
3. https://support.buildship.com/m/1328581590955331594
4. https://support.buildship.com/m/1324710666862596138
5. https://support.buildship.com/m/1249650035210190868
BuildShip AI Support
Have done that and it has brought back functionality, but it seems to be duplicating now 🤣 so where it should trigger once it triggers twice instead
try unship flow --> delete trigger --> add trigger and ship again.
No I tried that and it duplicated again.
okay, its a bug, we confirm
we'll fix
Sometimes there is a (202) where it checks for unread emails and also a successful (200) run on a new email... But at other times it does two successful (200) runs that are exactly the same, so it is capable of running as it should, just sometimes it doesn't.
@Gaurav Chadha hi Gaurav, not sure if this is the right area to ask the question. My Gmail Oauth is not working either. While I can confirm all scope of Gmail has been selected, it still says 401 unauthorised. I have revoked the access and re-initiated it a few times, still does not work. Could this be a similar bug?
this seems a different issue, could you please share it via in-app support request with a jam.dev recording showing 401?
@Chris Wright | Because You Can quick question, do you have a send gmail node in the flow just after the inputs or before output?
No in terms of the gmail action it is just the trigger