Had a bunch of incidents today where flows have got stuck at “running”, they don’t fail and due to the fact they get stuck we then end up hitting our concurrent limit - any ideas why this is happening and how to stop it. Example of one of our flows below;
https://www.gumloop.com/pipeline?run_id=WJCmspvvzXAX9jb8uYn8DS&workbook_id=kmwNxFDQ8RhC6kq2hdqof1
Hey @user7 - I’ve requested access to view the flow. You can also enable ‘anyone with the link can view’ under the share button. Will look into this once I’ve access 
Hi Wasay, thanks for replying - you say you have requested access to view the flow - how to I authorise access? Not keen to make it public just because the input is real resume data so I don’t want to share it publicly.
Hey! If you click share in the top left and then anyone with the link can link can view – you can view it before sending over yourself (in incognito mode if you’d like) to what is viewed by others!
https://www.gumloop.com/pipeline?run_id=3GRHYFaLiMUnp9c6mSSL49&workbook_id=kBQKk66Uy7SibJYaQpVta9
Shared this one today, the ones that are failing are the ones that don’t include the personal details, just job and employment history so shouldn’t be an issue.
Thank you for sharing! Looping @rahul-gumloop here to manually kill the flow. We’ll investigate this further.