Original Full Workflow - Added the 7:05 trigger as a dual path trigger today
7:05 Trigger Workflow - Succesfull today
15 Min Polling Workflow - Failed to trigger
we also definitely need to filter the search per date
seems like the third workflow (15 Min Polling Workflow) doesn’t have a trigger set up. Maybe it was deleted by accident?
It looks like I accidentally deleted the trigger while cleaning up my data-sources ! Oops
Could you try setting it up again and see if it’s working? Please report here or by Email Support if otherwise
Updated the trigger-- it should be active now
I’ll try a test email later today
Awesome, thanks!
Sent a test email this morning-- It looks like the full workflow (15 sec. polling) triggered & the 15 minute polling triggered successfully (with “to” line utilized)
This morning, the 7:05AM triggered 4 times keying off of events from yesterday. I decided to delete all files in the Gmail Label.
Awesome! At least it’s working even before the improvements are done. Thanks for confirming
The expected outcome tomorrow is that when the target email arrives at 7:00 AM-- the 7:05 trigger will fire & the 15 second trigger fire. I fear that the 7:05 trigger will fire 2x times since there will be 2 unread emails within the “Open Closed PO Level” label.
More to come
Hi - Can you outline the improvements your team is working on? I noticed this morning that the Log for the 7:05 Trigger successfully identified a new gmail attachment with label, but the Pipedream workflow did not trigger.
Hi , the improvement to the Gmail trigger was just released - you can see some of the changes in the PR here.
To update your source to the latest version, you will need to remove, and re-add the New Attachment trigger, and redeploy.
Thank you Michael-- Trigger has been updated in the Workflow. I’ll review the changes in GitHub
Please let me know if you’re still running into issues after the update, but I tested this on my side and it was working correctly for me.
i deleted the original trigger & replaced it with a new trigger (same gmail connection as before) but the workflow failed to trigger this morning. The Log successfully polled for new attachments, so the issue seems to be with the Constructing Attachment Query and/or passing to the Pipedream workflow
Sorry to hear that. Can you share a link to your workflow and enable sharing with support?
cc: in case you have any ideas on the above as well
That’s weird because as far as I can see it should log the retries if the message at the end is null 
I can try to update the getMessageWithRetry function to be more compliant with a try/catch block