Overview

The Send Test Message feature allows you to verify the email content, personalization, and configuration before activating the journey. This helps ensure that the message renders correctly and reaches the intended recipients.

You can use the Test option in two ways.

1. Action Node: You can send test emails directly from the Action node on the Journey canvas:

2. Channel Specific Action node in the Journey Builder.

• Email Action Node
• App Push Action Node
• WhatsApp Action Node (coming soon)

Test Email Configuration

The test panel allows you to specify who should receive the test email.

Recently used: You can add all the recently used emails from here without manually entering them.

Send the Test Email

After entering the recipients in the Email bar, Click Send. The system processes the request and attempts to send the test email.

A confirmation screen will appear including success or failure details for each recipient.

Email Send Test: Failure Scenarios

Below are the scenarios where a Journey Node Send Test for Email can fail

1. User Issues: A test email will fail if the user is anonymous and the anonymous feature is not enabled in the system.
2. Personalisation / Attribute Issues: If there is an error while reading user attributes or event data from MongoDB, the test fails with a personalisation error.
3. Template / Content Issues: If a merchandising template is used but the mt_request_id is not set in Redis, the test will be skipped.
4. Recipient Validation Issues: The test fails when the email address is invalid or improperly formatted.
5. Blacklisted contacts: The email is blocked if the recipient is unsubscribed or present in suppression lists.
6. Product Recommendation Issues: The test fails if product or recommendation data cannot be retrieved.
7. Coupon / Content Issues: The test fails when the coupon or dynamic content is invalid, missing, or exhausted.
8. Gateway Issues: The test fails if the email service provider or gateway is unavailable or encounters errors.
9. Backend Errors: Any internal service error or downtime leads to test failure.

Test App Push Configuration

Click Send Test to directly test the APN templates before making your journey live. Click the drop down menu of Test with to select between the two options below:

Primary Key Configuration

The test panel allows you to specify who should receive the test App Push Notification when the Test with selection is Primary key. The Primary key here is Email

Recently used: You can add all the recently used emails from here without manually entering them.

Push Token Configuration

Use this option when you want to validate delivery to a known device without requiring the recipient to exist as a contact in the system.

Enter the Push token comma separated or select from recently used.

Send the Test App Push

After configuring the Send Test tab with either Primary key or Push Token, Click Send. The system processes the request and attempts to send the test the App Push Notification.

A confirmation screen will appear including success or failure details for each recipient.

App Push Send Test: Failure Scenarios

Below are the scenarios where a Journey Node Send Test for App Push can fail.

1. Message template not loaded: The selected App Push template could not be fetched or rendered. Verify that the template exists and is published.
2. User attributes not loaded: The system could not retrieve user profile attributes required to render the notification. Check that the user exists and their profile data is populated.
3. Invalid or incomplete message: The notification payload is missing required fields such as title, body, or deep link. Review the template configuration and ensure all mandatory fields are completed.
4. Sandbox send limit reached: The test send limit for the account’s sandbox environment has been exceeded. Contact your account administrator to review sandbox quotas.
5. No push token found: No valid device push token is associated with the identified user. Ensure the user has the app installed and has opted in to receive push notifications.
6. Personalization / attribute error: A personalization tag in the template refers to a user attribute or event that is missing or could not be resolved for the test recipient.
7. Liquid render failed: The template contains Liquid syntax that failed to render due to a syntax issue, unsupported function, or null value. Review the Liquid logic used in the template.
8. No products found: The recommendation engine or product collection referenced in the template returned no products for the test recipient.
9. Dynamic carousel validation failed: The dynamic carousel payload did not pass platform-specific validation checks. Review the carousel configuration for Android or iOS compatibility.
10. Push not queued: The push notification could not be queued because the device platform, token, or routing configuration did not match the expected setup. Verify the push token and app platform.
11. Test flag or request ID missing: An internal identifier required to process the test send is missing. Retry the test send. If the issue persists, contact support.
12. Duplicate job suppressed: An identical test send request is already being processed. The duplicate request was suppressed to avoid duplicate delivery.
13. Infrastructure or configuration issue: A backend issue such as a database failure, cache issue, configuration problem, or client restriction prevented the test send. Contact your Netcore CE administrator or support team.

Test WhatsApp Configuration

Click SEND TEST on the WhatsApp Action node to validate your template with real personalization before making your journey live.

To configure the Send Test node, refer to the table below:

Send Test Message

After selecting the recipients, click Send. The system validates the request and attempts to deliver the WhatsApp test message.

Once processing is complete, a confirmation screen displays the delivery status for each selected recipient.

WhatsApp Send Test Failure Scenarios

A Send Test request can fail in the following scenarios: