I wonder if can help me out testing the update?
Hi - Apologies for the delay. I can update my triggers today + redeploy my workflow.
Do I need to create an entirely new Custom Oath Source to test the update?
Yes, you’ll just need to remove the source and re-add it to pick up the newest version.
Hi Michael / jcortes–
Seeing the same issue with Version 0.0.9. Logs report received 1 new message, but failed to run workflow.
Is it possible that this is a scheduling issue with Gmail app? currently I have ~4 triggers polling gmail at the same time (7:05 AM). I can stagger if that’s expected product behavior, but I’d prefer to understand the root cause here to avoid issues in future workflows.
Hi what do you mean by failed to run workflow?
The trigger logs identify a new attachment, but the workflow that uses the trigger didn’t start.
Michael Thorson are you able to pull, deploy and test the version in this PR right here? [FIX] gmail_custom_oauth: Source New Attachment Received: Fixed getMessageWithRetry to support try/catch block instead by jcortes · Pull Request #12405 · PipedreamHQ/pipedream · GitHub
The PR is still in Ready for QA so we are wating to be deployed in production
but I guess in the meantime you can test it
Ok one sec I’m deploying the component to production right now, give me.a sec I’ll let you know when it is available
we’ve just deployed the latest version of the component it should be version 0.0.10 can you please test it again, thanks in advance!