Testing Engagement Program

[Anonymous]

I am trying to test our engagement program, with some dummy emails and myself and 2 coworkers as the only members.  I have it set up to send every day, and am having some serious issues already. First day, only 1 of the 3 people received the email, despite Marketo saying 2 were in the cast (though not 3?). Second day, 2 of 3 received the email. Third day no one received it, Marketo saying 1 was in the cast. We aren't even at the 4th day yet and it's showing 1 in the cast.  I don't get it.... What am I missing?  The emails aren't blocked from emails, all are members of the engagement program... Help!

[Anonymous]

Is you steam made up of emails or programs? -Mark

[Anonymous]

Have you confirmed that they are not unsubscribed?  Do you have communication limits set?  We also built a feature specific for testing nurture. Here is the information....

[Megan_Reed1]

If using the "test stream" option, you actaully have to push the "run cast" each time to get the next email. I do not believe it uses the stream cadence.  Cheryl's article runs through those steps.

[Anonymous]

Seems as though it may be the communication limits that are throwing things off.  Can i use the Test Stream function to send to more than one person?

[Anonymous]

Now I've run through the Test Stream and it only seems to send stand-alone emails, not ones within a program that i've added to the stream (added the program and specified a smart campaign within that program).  I don't understand what's going on here.

[Anonymous]

Is this still the case? I'm having a lot of trouble testing an engagement program (EP) stream that consists of nested programs with emails in them. Not getting any of the emails. Does the "Test Program" functionality only work for emails within an EP and not nested programs?

[Anonymous]

I talked to a support engineer and he clarified that the content in a stream, at least nested programs, has to be activated to use the "Test Stream" functionality, in case anyone else is getting stuck on this step. I didn't see this explicitly outlined in the documentation.