Delaying completion of a flow until request campaign's flow completes? | Community
Skip to main content
Matt_Stone2
Level 9
September 8, 2017
Solved

Delaying completion of a flow until request campaign's flow completes?

  • September 8, 2017
  • 1 reply
  • 3530 views

I'm assuming the normal behavior of a Request Campaign flow step is to run the requested campaign (Campaign B) in parallel with the campaign that requested it initially (Campaign A)? Is there a way to tell Campaign A to pause its flow until Campaign B has finished its flow?

Essentially there's dependencies at the end of Campaign A that are only fulfilled by Campaign B finishing. I could add a wait step, though I'd rather avoid it if possible.

Campaign ACampaign B

1. Change Data Value

2. Change Data Value

3. Request Campaign

4. Interesting Moment (uses field A)

1. Change Data Value (field A)

My main concern is that with high enough traffic, field A will get out of sync with these flows and the interesting moment will be incorrect. Any ideas/suggestions?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Josh_Hill13

This is part of the race condition. Yes, it will run as soon as you request Campaign B.

In order to slow it down, you can either

  • Put a wait step at the top of Campaign B to allow A to finish. 4 to 10 minutes is often enough.
  • Request Campaign at the END of Campaign A instead.

there is no Order of Operations than doing this.

Remember that ANY Wait Step longer than 4:59 will cause the campaign to drop in the Campaign Queue priority list.

1 reply

Josh_Hill13
Josh_Hill13Accepted solution
Level 10
September 8, 2017

This is part of the race condition. Yes, it will run as soon as you request Campaign B.

In order to slow it down, you can either

  • Put a wait step at the top of Campaign B to allow A to finish. 4 to 10 minutes is often enough.
  • Request Campaign at the END of Campaign A instead.

there is no Order of Operations than doing this.

Remember that ANY Wait Step longer than 4:59 will cause the campaign to drop in the Campaign Queue priority list.

Dan_Stevens_
Level 10
September 8, 2017

Josh, I think you meant to say put a wait step here - in campaign A - to allow the requested campaign (campaign B) to run fully:

Basically, step 4 is dependent on step 1 in campaign B

Matt_Stone2
Level 9
September 8, 2017

That's right, Dan. Per Josh, sounds like the wait step is the only option here -- I just hoped to avoid delaying everything longer than absolutely necessary.