Flows stuck in progress

#1

I have been having flows get stuck in progress lately.

https://goo.gl/J4LW1c

Don’t know what’s causing it.

(Karen Barker) #2

Hi there,

Do the flows ever complete? What is the last action shown in the logs - could there be a question or a wait task that is stopping the flow completing yet?

We recently added the “in Progress” status for an interaction so that you have visibility of all actions that have currently run before the flow completes.

(John Lutz) #3

Yes, 9 hours later.

(Karen Barker) #4

Hi John,

When you look at the detailed interaction logs for the flow which was stuck “In Progress” the time stamps should show when each action was completed. If you want to share these with me I’ll happily take a closer look and see if there was any reason for the flow to seemingly get stuck. :slight_smile:

#5

Hi Karen,

I’m experiencing the same issue. All flows get permanatly stuck (“In Progress”) when using the “Trigger a Flow” function. Everything else seems to be working as expected. I’ve been in touch with Daniel over email so hopefully it’ll be resolved soon as we rely heavily on it working properly. Cheers Paul

(Karen Barker) #6

Hi Paul,

We have identified an issue with the “Trigger a Flow” action if there is no Response Path included. This usually occurs if the flow is triggered by an action occuring other than a user sending the bot a message. We are working to get this fixed ASAP and as soon as I have any further information I’ll let you know.

In the meantime if you add a valid response path to the trigger a flow action the flow should trigger successfully. :slight_smile:

#7

Hi Karen,

Unfortunately that solution doesn’t work - I’ve added response paths to the trigger actions but the flow still gets stuck displaying “In Progress” when it attempts to run the trigger action. This is now getting urgent… do you have any other possible solutions? Cheers Paul

(Karen Barker) #8

Hi Paul,

That’s strange whenever I’ve tested this way the flow has successfullly triggered. Unfortunately there isn’t another workaround for this at the moment. If you could please email us at support@flowxo.com, sharing your flows so we can see exactly how you have this set up then we may be able to see why it isn’t working for you. Thanks :slight_smile: