Access and subscribe to system alerts alerts

When building your journeys and campaigns, use the Alerts button to check and resolve errors before executing or publishing them:

From the dedicated Alerts menu, you can also subscribe to Adobe Journey Optimizer system alerts as detailed on this page.

Access alerts access-alerts

When a failure happens, you can get system alerts in Journey Optimizer notification center (in-app alerts), and/or receive an email. To access these alerts, follow the steps below.

In the left menu, under Administration, click Alerts. Several pre-configured alerts for Journey Optimizer are available.

They are listed as follows and each alert is detailed below.

Subscribe to alerts subscribe-alerts

Based on the subscriber’s preferences, alerts are sent by email, and/or directly within Journey Optimizer notification center, in the top right corner of the user interface (in-app notifications). Select how you want to receive these alerts in the Adobe Experience Cloud Preferences. Learn more

When an alert is resolved, subscribers receive a “Resolved” notification.

Manage alerts manage-alerts

To manage alerts, select an item and use the More actions button.

{width="80%"}

By default, all alerts are enabled. To disable an alert, select the the Disable alert option from the More actions menu. All subscribers to this alert will no longer receive the related notifications.

Select Manage alert subscribers to view the list of users who subscribed to the alert. Use the blank field to add more subscribers.

{width="80%"}

The possible alert statuses are listed below:

Journey alerts journey-alerts

Journey Custom Action Failure alert-custom-actions

This alert warns you if a custom action fails. We consider there is a failure where there has been more than 1% of errors on a specific custom action over the last 5 minutes. This is evaluated every 30 seconds.

Alerts on custom actions are resolved when, over the last 5 minutes:

The I/O event subscription name corresponding to the custom action alert is Journey Custom Action Failure.

To troubleshoot Custom Action alerts:

Read Audience Trigger Unsuccessful alert-read-audiences

This alert warns you if a Read Audience activity has not processed any profile 10 mins after scheduled time of execution. This failure can be caused by technical issues, or because the audience is empty. If this failure is caused by technical issues, be aware that retries can still happen, depending of the type of issue (eg: if the export job creation has failed, we will retry every 10mn for 1h max).

Alerts on Read Audience activities only apply to recurring journeys. Read Audience activities in live journeys that have a schedule to run Once or As soon as possible are ignored.

Alerts on Read Audience are resolved when a profile enters the Read Audience node.

The I/O event subscription name corresponding to the Read Audience Trigger Unsuccessful alert is Journey read audience Delays, Failures and Errors.

To troubleshoot Read Audience alerts, check your audience count in the Experience Platform interface.

Configuration alerts configuration-alerts

AJO Domain DNS record missing alert-dns-record-missing

This alert notifies you when critical DNS records (NS or CNAME) required for proper deliverability configuration are missing or misconfigured. Without these records, email deliverability may be compromised.

The AJO Domain DNS record missing alert is triggered when the system detects that the required NS or CNAME records are absent or do not match the configuration standards.

If the changes do not resolve the issue, the same alert will be triggered again the next day.