DocumentationTutorialsUse Cases & Blueprints

Run the workflow

Last update: September 14, 2026

CREATED FOR:

  • Developer
  • User

Objective

In the next few steps you learn how to test your workflow and more importantly your SMS activity using test mode.

Verify workflow

  1. The final workflow looks something like the following when you are done. Double-check everything looks good. You see:

    Final workflow canvas ready for testing

  2. If you haven’t already stopped your workflow, click the Stop button in the upper right.

    Stop button in the upper right of the workflow

    note
    NOTE
    Optionally, try clicking on the Restart button, but it’s likely you’ll see an error since you’ve added activities after the workflow was created, and its cache is no longer valid.

  3. Next click the Start button to execute and test the workflow end-to-end

    Start button to execute the workflow test

  4. 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.

    Left Result transition selected before the SMS activity

    Preview results button in the right rail

  5. You see 33 records and the targeting dimension matches the Customer ID (the join key to profile)

33 records with targeting dimension matching Customer ID

Test the SMS activity

  1. Close out of the previous window and click on the SMS activity and then click the Run test button in the right rail

    Run test button on the SMS activity

  2. Almost immediately, a new button appears labeled View report. Click the View report button to launch into the report screen.

    View report button for the SMS activity test

    note
    NOTE
    This screen is not populated initially as it takes some time to execute the test run. You may need to refresh a few times before you see results.

  3. When you get results, you see 100% were targeted!

    SMS test send results showing 100 percent targeted

    Wait, a minute…the incoming result was 33 records so where did the 4 go?

  4. 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.

    Re-reviewing the transition results after the SMS test

  5. In the Preview results screen scroll all the way to bottom of the table and you notice that 4 records have a blank Targeting dimension.

4 records with a blank targeting dimension at the bottom of the table

Explanation

Here is what happened.

  • You had 33 customer lines that you wanted to send an 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 look up a profile or create a new one immediately

Result --> Orchestrated Campaigns drops those 4 records on message execution

NOTE
There is an enhancement coming to help address this issue in two ways:
  1. Make sure an exclusion log is created for records that are missing a targeting dimension on send
  2. Update the Change dimension activity to do an inner join vs. external join which would drop those 4 records up front
SUCCESS
Congratulations! You are now officially certified to launch your very own Orchestrated Campaigns and broadcast messages to the world—responsibly. Now you can market with confidence!

Publishing the workflow

You are not going to do this in the lab, but for context here is what happens at publication time:

  1. Scheduler kicks in if the campaign has a schedule set

  2. Save Audience activities create the audience shell within the Audience Portal and the qualified profiles start ingesting

  3. 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

recommendation-more-help
blueprints-learn-help-blueprints