Stopping Flow #1 after moving into Flow #2

(Tyler C Hurst) #1

Hi there!

I seem to be running into an issue where I cannot stop Flow #1 from continuing despite triggering Flow #2.

In Flow #1 I have shortcuts that trigger keywords for Flow #2. I also have a Wait and Send Message telling the user to ask for “help” if they are stuck.

The issue is, If a user uses the shortcut/keyword to get into Flow #2, the Wait and Send Message that remained in Flow #1 plays in the middle of Flow #2. How do I prevent that from happening?

Thanks!

(Daniel Beckett) #2

Hi Tyler.

You could set an attribute when your second flow is started, i.e. “started = true”. In the first flow just after your wait action you can then have an action with a filter to stop the flow if the started attribute = true. On filters there is a checkbox for ‘Also stop rest of flow if conditions are met’ that you can enable.

(Tyler C Hurst) #3

Got it, that makes sense.

Assuming I also have a few other flows (Flow #3, Flow #4, and Flow #5) that function the same way as Flow #2 and each have their own Wait -> Help message segments…

how would I ensure this is true if any, or even ALL, of those other flows are started?

(Daniel Beckett) #4

Attributes are saved against the user’s response path so if you set the same attribute name it’ll be available across all flows.

Since you’ll want the user to be able to trigger other flows again you’ll want to make sure you clear the attribute at the end of the flow, i.e. set the value for ‘started’ to be empty.