Email notifications aren’t sent due to an empty recipient group in AEM Cloud Sites
Adobe Experience Manager (AEM) Cloud Sites may not send workflow email notifications in non-production when the configured recipient group resolves to an empty list because of missing group membership, absent email addresses, or configuration differences between environments. To resolve the issue, verify the recipient group, membership, email properties, and related configuration in non-production, then repeat the workflow action to confirm that recipients are resolved.
Description description
Environment
Adobe Experience Manager (AEM) Cloud Sites (non-production and production environments)
Issue/Symptoms
- After a successful workflow action in a non-production environment, administrators or intended recipients don’t receive the expected email notification.
- The same workflow and codebase function correctly in production, where emails are received as expected.
- Workflow logs in the non-production Author instance show that the email service is invoked, but the recipient group resolves to an empty list, preventing email delivery.
- The workflow action completes successfully; only the notification email is missing.
Root cause
The email workflow in the non-production environment doesn’t send notifications because the recipient group resolves to an empty list. This typically occurs because of missing group membership, absent email addresses in profiles, or configuration differences between non-production and production environments.
Resolution resolution
Follow the steps below to resolve the issue:
-
In the non-production Author environment, go to Tools
>Security>Groups. -
Search for the recipient group configured in the workflow.
-
Confirm that the group exists and contains the expected administrators or nested groups.
-
For each intended recipient, verify that a valid email address is populated in their profile.
-
Compare the non-production and production configurations for the recipient group:
- The group or recipient name configured in the workflow.
- Group membership and profile email properties.
- Any group mapping or synchronization settings.
- Any RepoInit or application configuration used to create the group.
-
If the group is IMS-managed, confirm that the IMS group and non-production Author product-profile mapping are correct and that the group has synchronized to the non-production Author instance.
-
If the group is a local AEM group, ensure that it’s created or deployed in non-production using the same supported mechanism as production.
-
After correcting the recipient configuration or membership, repeat the workflow action and check the non-production Author log. The
Final resolved recipient listshould contain one or more valid email addresses. -
If the recipient list is populated but the email still isn’t received, collect new non-production Author logs that cover the workflow execution and continue investigating mail-service, SMTP, or networking issues.