Dan, if it's any help, I was under the impression that request campaigns function separately and those do not need to complete before going to the next step in the original campaign. Just the act of requesting the campaign needs to complete, then the next flow step is actioned.
It is certainly frustrating when there is conflicting information received from consultants!
Sorry for not answering earlier, but connections for us in Europe are still difficult.
I concur, the "request campaign" is a "fire and forget" flow step and the called campaign will run it's own life totally independantly from the calling one.
Dan, it was always my understanding that the called campaign functions independently of the calling campaign. I have never heard anything otherwise.
Both Ed and I have written about this
Smart lists on the other hand, do have to wait for all nested smart lists to be tabulated before giving a final count.
I'd say file a Support ticket. It's going to be hard to diagnose without being able to see the whole campaign, how the lead qualified for the campaign, and the source of the qualification (if it's a trigger campaign that is sending the email).
I strongly suspect that you are having duplicates in your database. The lead Tom Tolios is present twice in the campaign and therefore the trigger is called twice.
To check this hypothesis, click the lead name in the results. The lead detail pages will open and you will be able to check form the URL if the lead ID's are the same.
The strange thing here is that:
- the lead is not a duplicate
- the smart campaign is not used for other webinars then only this specific webinar
I did request a support ticket, but the support agent is facing the same issues as I am. They have not been able yet to resolve.
The smart campaign is triggered by "Fills out form X". A lead can only run through it once.
After the wait step with the token, the email should go out.
The only 'new' thing about this set up for me is the usage of tokens in the wait step, but I cannot imagine that to cause an email to be sent twice.
I sent a message to the agent helping you as well, but it looked like you triggered the campaign twice a few minutes before you switched the campaign setting to only allow someone to run through the flow one time. You've had two iterations of your record hanging out and exiting together in your Wait steps.
Thanks for helping out!
This could be a reason yes. I did see, however, the support agent having the same issues with the email being sent twice.
I think for now I should set up another campaign, and test it again. See if the issue happens again.
Her situation was different. Your wait steps are set to wait for a specified date, but that date is now in the past, so her lead record just kept moving through the flow. Step #6 and Step #8 send the same email so she got them in succession. If you check the Step IDs on those emails you'll see they are different.