Run the Workflow
objective in the next few steps you will learn how to test your workfow and more importantly your sms activity using test mode verify workflow the final workflow should look something like below when you are done double check everything looks good you should see if you haven't already stopped your workflow ensure you do so now by clicking the stop button in the upper right optionally you can try clicking on the restart button but its likely you will see an error since you've added activities since the workflow and its cache is no longer valid next click the start button to execute and test the workflow end to end review the result coming into the sms activity by clicking on result (there are two results so use the left one as shown below) and then in the left rail clicking on preview results button you should see 33 records and the targeting dimension matches the customer id (the join key if you will to profile) test the sms activity close out of the previous window and click on the sms activity and then click the run test button in the right rail almost immediately you will see a new button appear labeled view report click the view report button to launch into the report screen this screen will not be populated initially as it can take roughly 10 minutes for this to complete its test what is happening at this point is the final population coming into the sms activity is being joined to the real time customer profile and validated to ensure its allowed to be sent, the phone numbers are valid, consent is there, etc the final results will include a view of how many messages are to be sent and any reasons for exclusions when you do get results you should see 100% were targeted! \<font color="#ef4444">wait, a minute the incoming result was 33 records so where did the 4 go?\</font> go back to the workflow canvas and click on the transition result coming into the sms activity and then click on preview results in the right rail in the preview results screen scroll all the way to bottom of the table and you'll notice that 4 records have a blank targeting dimension explanation so here is what happened you had 33 customer lines that you wanted to send a sms message after the change dimension activity 4 of those customer lines had no associated customer account the join to the real time customer profile requires you have a customer id and since there is none on those 4 records there is no way to lookup a profile or create a new one on the fly result > orchestrated campaigns drops those 4 records on message execution there is an enhancement coming to help address this issue in two ways make sure an exclusion log is created for records that are missing a targeting dimension on send update the change dimension activity to do an inner join vs external join which would drop those 4 records up front publishing the workflow you are not going to do this in the lab, but for context here is what happens at publication time scheduler kicks in if the campaign has a schedule set save audience activities create the audience shell within in the audience portal and the qualified profiles start ingesting message execution starts for the first message activity in the workflow profile lookups occur against the profile snapshot matching profiles honor the consent found on the profile non matching profiles are created on the fly delivery logs are created in the ajo message feedback event dataset