Skip to main content
Menu

Hi guys! 

I need a quick confirmation about how smart delays changing behave for users who are already inside the flow.

Context (today is Aug 19):

  • The first smart delay is set to the morning of Aug 20 — this date was the same in the original flow and remains unchanged.

  • All subsequent smart delays and messages have been updated to the new schedule for Sept 2 (texts and dates are edited in the same flow).

Questions:

For contacts who are already inside a smart delay (Aug 20 delay): will the engine use the updated date/time I saved in subsequent smart delays, or the date/time that existed when they first entered the flow?

And do I need to apply a “blocked” tag to stop the existing cohort as I was advised by support team? I’m really confused.

 

If there’s a best-practice here, I’d appreciate your recommendation. Thanks a lot!

​@El Zhene you’ll need to add the condition to block them, as the smart delay has already started and can’t be stopped or changed (it’s a timer that’s running already).

In general, when you have multi-step flows like that, the best practice in my opinion is to split it into different automations, and then connect them with the ‘start automation’ step. This lets you make changes to the automations down the line much easier.

Hope this helps!

 

​@Gustavo Boregio thank you very much. I set up exactly like you advised me but look what message I’ve got from support team: The contacts will follow the new version of the automation, meaning that once they finish the Aug 20 delay, they’ll continue through the flow using the updated dates and content you’ve saved. In other words, they won’t “carry” the old schedule with them; they’ll always experience the most recent version of the flow at the moment they reach each step. Now I confused more because I already have two flows and still don’t know what is right. Could you please give a feed back if I set it up correctly? Condition blocks before every smart delay in the old flow and skiping first messages by the tag web280825 in the new flow

 

Reply


Community Terms & ConditionsCookie settings