Hey @mutty! 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.
Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}}
Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
Provide details about the issue—more context helps us troubleshoot faster.
Hey @mutty — mind sharing your workbook? Also, how often is this happening and since when? We recently rolled out a bunch of improvements to trigger reliability, so if you could revoke and re-auth with Drive once on the credentials page, then re-enable the trigger, that’d be great.
If you still need to re-auth after that, definitely let me know. And I’m guessing there aren’t any run links for this — do you manually check if the run didn’t trigger and then find the auth issue? Would appreciate a bit more context here.
This is in my client’s workbook and they have 3 workflows that should be triggered on a daily/weekly basis. I’ll follow the instructions you’ve given and see if it still occurs.
We manually check after a couple minutes when the expected output hasn’t it the destination we’ve set. At that point, we try to run it manually which usually results in Google Drive Folder Reader Failed!.
Gotcha. We did ship an improvement here, should be live in our next update (end of this week hopefully). Also, Loop Mode does not seem necessary here since the trigger only picks the single uploaded file, wouldn’t make a difference to the flow but just highlighting if you want to make the flow efficient.