SOLVED

Multiple Request Campaign Flow Actions

Go to solution
Highlighted

Multiple Request Campaign Flow Actions

Hi All,

If we have a smart campaign which has two request campaign flow actions (see example below).  Would Campaign 1's flow complete, meaning the wait of 5 minutes and the change of the data value, before Campaign 2 is requested or would Campaign 2 would get requested immediately after Campaign 1 is requested?

Flow Action Step 1: Request Campaign 1

    1. Campaign 1's Flow
      1. Wait 5 minutes
      2. Change Data Value

Flow Action Step 2: Request Campaign 2

    1. Campaign 2's Flow
      1. Change Data Value

Thanks!

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Level 8 - Champion Alumni

Re: Multiple Request Campaign Flow Actions

Hey Nate Oosterhouse​,

If I understand you correctly, there are two smart campaigns (Campaign 1 and Campaign 2) that are being requested in sequence from a third campaign and you are asking about order of operations of the flow steps within Campaigns 1 and 2.

The answer in this scenario is that the order of operations is completely independent. Both campaigns will be requested in sequence and then the flow steps within them will be processed by the system based on when they were initiated, their priority, the current backlog etc.

Given the wait of 5 minutes in in Campaign 1, it is highly unlikely that the first data value change will be complete before the one in Campaign 2.

If you want to control the execution of Campaign 2, do not request it but have the trigger be the data value changing in Campaign 1. This ensures that there is no way it will start before Campaign 1 is finished.

---

Justin Norris | Perkuto​

View solution in original post

4 REPLIES 4
Highlighted
Level 8 - Champion Alumni

Re: Multiple Request Campaign Flow Actions

Hey Nate Oosterhouse​,

If I understand you correctly, there are two smart campaigns (Campaign 1 and Campaign 2) that are being requested in sequence from a third campaign and you are asking about order of operations of the flow steps within Campaigns 1 and 2.

The answer in this scenario is that the order of operations is completely independent. Both campaigns will be requested in sequence and then the flow steps within them will be processed by the system based on when they were initiated, their priority, the current backlog etc.

Given the wait of 5 minutes in in Campaign 1, it is highly unlikely that the first data value change will be complete before the one in Campaign 2.

If you want to control the execution of Campaign 2, do not request it but have the trigger be the data value changing in Campaign 1. This ensures that there is no way it will start before Campaign 1 is finished.

---

Justin Norris | Perkuto​

View solution in original post

Highlighted

Re: Multiple Request Campaign Flow Actions

Thanks Justin.  Appreciate it

Highlighted
Anonymous
Not applicable

Re: Multiple Request Campaign Flow Actions

Justin Norris We have a situation similar to this - calling 5 separate Request Campaigns in a sort of "Master Campaign." We've encountered issues with them running out of order. I've looked at what you mentioned here (and have seen it elsewhere) about triggering based on data value change. This is what I want to do, but for us, the data value may or may not actually change. Will the data value changed trigger still fire if it *attempted* to? Example:

Sending out a campaign for John (Sales) in Bob's name (SDR)

request campaign to change email

request campaign to change first name triggered by data value changed (email)

request campaign to change last name triggered by data value changed (first name)

This may have been done previously for a different campaign, so the email might not change at all. Will this still run?

Highlighted
Level 10 - Community Moderator

Re: Multiple Request Campaign Flow Actions

This may have been done previously for a different campaign, so the email might not change at all. Will this still run?

No. A no-op isn't considered a change because... it isn't a change.

It sounds to me like you should start a new thread  Tell us your core functional requirements (rather than describing the current, not-quite-right technical implementation) so we can help you decide the best way to get what you need.