Thanks for the response. Here is some additional info. Yes. It is a program that I dropped into the stream. There are conditions in the smartcampaign that limit the geos. e.g. if asia, send this mail. Wait 7 hrs If Europe, send this mail. Wait 8 hrs If US or blank region, send this mail. There are other programs in the stream that would work the same way. Different emails/content, but the same general flow. It is going to be an ongoing effort. i.e. we will continue to add content (programs) to the stream. With your #3, are you thinking of three programs in the stream. One for each geo. Their smartcampaigns would still need the delays in them, since they all have to go off the stream cadence. But it sounds like you are not aware of any general best practices for using wait steps with large sends. i.e. will the number and length of wait steps will not cause delays with larger numbers of leads in the stream. Do they do something like this: Filter entire qualified list, process entire list (but really only send what is applicable), wait, filter whole list again and process whole list, etc. If it was doing that, I could see how it could slow things down, especially with large lists as it may have one send piled up on another. But I am not an app architect. Because if is was a simple filter, process and send only to applicable, wait, filter, process and send only to applicable, etc. it should not matter how many wait steps you have, how long they are, or how many leads you are processing. Thanks! I know we are going deep in this one.
... View more