Actions Center actions-center

AEM as Cloud Service sends Actions Center email notifications when critical incidents occur that require immediate action, and proactive recommendations for optimizations. Examples include a blocked queue, or an expiring set of credentials; the full set of Actions Center notification types can be viewed in the table below, which will expand over time.

When an Actions Center email notification is received, it can be clicked to open AEM as a Cloud Service’s Actions Center with a pop-up displaying additional context explaining the action for a customer to take.

In addition to displaying information about the just-clicked email notification, the Actions Center serves as a hub where you can view and manage the set of current and older notifications.

There are two high level categories of notifications that appear in the Actions Center:

  1. Operational incidents - an event has occurred, which typically requires prompt resolution. For example, resolving a blocked queue.
  2. Proactive recommendations - Adobe has a recommendation for an action a customer should take in the near future. For example, to stop referencing a deprecated UI.

See the table below for the notifications currently supported in Actions Center.

From the Actions Center, you can select a specific program and environment, which has the effect of filtering for that scope.

Configuration configuration

To configure receiving Actions Center email notifications, create the Product Profiles described in this article, namely Incident Notification - Cloud Service and Proactive Notification - Cloud Service. Also assign the appropriate Adobe IDs from your organization to those profiles. This allows an administrator to determine which users qualify to receive these email notifications.

Actions Center email notifications function at the organization level so subscribers will receive notifications for all programs and environments within those programs.

Detailed User Flow detailed-user-flow

Clicking on the email will bring you to the Actions Center, with a pop-up showing context for the notification you clicked on and in some cases, links to additional information describing how to take corrective action. You can also access Actions Center directly at, where you can select the relevant program and environment.

Incident details

Clicking the Learn More link navigates the user to this article, where the notification type can be referenced in the supported notification types table below, which provides guidance on what action to take.

In the Actions Center, you can see a list of other recent notifications. It is recommended that using the Actions list, you acknowledge a notification to signal to Adobe that your organization is aware of the task, and to later resolve the notification when corrective action has been taken.

Notification list

In most cases, the pop-up should provide all the necessary context to resolve the issue. However, if there are questions for Adobe Support, you can click the Contact Support link in the pop-up. This will bring up a form from where you can describe the question and submit it to create a Support ticket, which will also include a reference to the specific notification so an Adobe Support Engineer has the relevant context.

Contact support 1

Contact support 2

Like all support tickets, it will appear in the Adobe Admin Console’s Support Cases tab, where you can track it and add additional comments.

Admin Console Support

Which Notifications Appear? which-notification

AEM as a Cloud Service has several types of notifications, but only a subset appears in the Actions Center, as illustrated in the table below.

Notification Type
How to configure
Appears in Actions Center
Operational incidents
Critical incidents requiring immediate action
User assigned to “Incident Notification - Cloud Service” product profile
Proactive recommendations
Optimizations that should be planned
User assigned to “Proactive Notification - Cloud Service” product profile
Cloud Manager pipeline statuses
Information about the state of your pipelines
User with Business Owner, Program Manager, or Deployment Manager roles, “Others” checkbox selected in Experience Cloud Preferences, as described here.

Supported Notification Types supported-notification-types

The following table lists the notification types currently supported in Actions Center. Notifications are currently limited to production environments.

Notification Type
Related Product Profile
Corrective Action
Blocked replication queue
Unblock queue by following instructions in the Replication Documentation
Invalid persisted GraphQL query
Fix the invalid GraphQL query by referencing the Persisted GraphQL queries troubleshooting documentation
Traffic spike at origin
Protect your origin by configuring rate limit traffic filter rules that trigger at lower thresholds than the default traffic spike at origin alert. See the Blocking DoS and DDoS attacks using traffic rules section of the Traffic Filter Rules documentation, which references a tutorial.
Pages contain a large number of nodes
Reduce total number of nodes within a page. Refer to Page Complexity documentation
Large number of running workflow instances
Terminate running workflows that are no longer needed. Learn how to configure a purge job
Expiring S2S certificate
Learn how to refresh a credential in the Generating Access Tokens for Server Side APIs documentation
Deprecated Service User Mapping
Learn how to use the newer Sling Service User Mapping format, as indicated in Best Practices for Sling Service User Mapping and Service User Definition
High Connection Count
Learn about connection pooling in the Advanced Networking documentation
Users added directly to custom group
Users need to be added to relevant IMS Groups and these IMS groups need to be added as members of AEM groups. Align with IMS best practices
Missing JCR content
Add missing JCR Content node. Refer to Assets Content Validator documentation
Completed workflows not purged
Minimize number of workflow instances and improve performance by purging workflow instances that are more than 90 days old. Learn how to configure maintenance tasks
Missing Sling resource type in Page
Add missing Sling resource type node. Refer to Assets Content Validator documentation