Hi there,
I’ve built this flow with a Typeform submission as it’s trigger. When I run it as is without submitting a new response, it does nothing. And when I submit a new typeform response, it also does nothing.
It just says “running” and doesn’t do anything.
Can you help?
Cheers,
Chuk
Hey @hallixrap! 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.
You can find your run history here: https://www.gumloop.com/history
Hey @hallixrap – There was a transient issue here. Do you mind disabling the trigger, enabling it again and giving it another try?
Apologies for the trouble here!
Thanks Wasay, now having the same trouble with this flow: https://www.gumloop.com/pipeline?folder_id=iMKPUJurhcS2BcRGmEYHEx&workbook_id=4T3KapwB59VYFYsYLFUabB&run_id=SgkbVEZJnreRSd8rYRAff4 - it seems frozen
Hey @hallixrap – Do you mind giving it another run please?
Yep, it’s working now! Do I need to go to my other workflows and review any held runs?
Nope. All stalled runs will be terminated automatically.
Thanks Wasay - off track but can you help me with this set up: https://www.gumloop.com/pipeline?workbook_id=4T3KapwB59VYFYsYLFUabB - I’m trying to make it work that when I upload a new text file into the drive, it analyses the file and gives me the output I need. If I do it manually, by clicking “run”, it works. Otherwise, if I do a trigger, it fails or if I use loop, there’s a mismatch with different nodes expecting different input. Any help?
Hey @hallixrap – Would you have a run link you can share when it fails due to the trigger? You can find run links from the Previous Runs Tab:
One reason why it could fail when the trigger is enabled is because the Run Code node is expecting a List input from the Drive Folder Reader node, which is the default output type when the trigger is disabled since it reads all files, however when the trigger is enabled, the output type is a singular file (ie. String/Text not List/Array). You might want to consider adjusting the code to account for both cases by checking the data type of the input.
Let me know if this makes sense and works for you 
