I have a few flows that say “Done” on the main history page, but when I click on the run to see the details, it says that one of the subflows are still running and it has been for 20 minutes now. See Attached. (I have a node in that subflow that has an error catcher and then sends me a slack notification, and as you can see that node was activated so there was probably an error, but because it still says “running” I can’t see what the error was).
Hey @SimonSays! 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 Simon, thank you for flagging this!
It looks like the workflow got stuck–chances are it was running on a pod that crashed. That’s very rare and we’re already on it. When you get a chance, could you run the flow again and see if it works now?
I’ve added some extra credits to your account to make up for the trouble 
Hi Wasay,
The flow ran twice this morning (10:44am and 11:52am EST) and the same issue happened.
