We added a (a) timing [90 days] and (b) action [email] to the end of a flow. I have a question regarding back-populating those who were in the flow but have by now exited (because these new steps weren't there originally).
I see from the how-to that this should be possible:
You do not need to back-populate if you add a new message to the end of a flow (or a single path) and want those currently moving down that path to receive that message. You would only need to back-populate to send to those who have either exited the flow or continued past the point of the new message.
This is exactly what we need to do.
But, when I go to the how-to on back-populating for list-triggered flows, from the two options it's not clear which accomplish the above in bold:
The first option is similar to back-populating metric-triggered flows; it schedules recipients for the step they would be at if the flow was live when they joined your list or segment. If your welcome flow lasts for 10 days, someone who joined two days ago will be scheduled at the two-day mark while someone who joined eight days ago will be scheduled at the eight-day mark. If they fall outside the flow’s timeline (e.g., they joined 20 days ago), they will not be added to the flow.
The second option, scheduling relative to when you click back-populate, will treat recipients as if they just joined the list or segment, so they will start from the very beginning of the flow. They will then travel through the flow just like any other recipient.
Any help is appreciated.
Best answer by elisegainesView original