Notification delivery issues for Legacy Perform & Engage customers

All affected customers have now been successfully migrated to Azure Communication Services and have been informed of the change.
Email notification delivery has been restored for the impacted organizations, and no further action is required from customers.

If you have any questions or experience any further issues, you can always create a support ticket through our Help Center.

We have identified an issue affecting email notifications for customers using the legacy Perform & Engage (Weekly10) notification configuration.

Our investigation found that Amazon Web Services (AWS), which supports this legacy email infrastructure, flagged an issue with the associated account and temporarily paused email sending from this service. As a result, some notification emails sent through the legacy configuration may not be delivered.

Customers using the default notification sender (noreply@365.systems) are not affected.

As a mitigation, we are proactively migrating affected organizations from the legacy configuration to the default notification sender and notifying impacted administrators of the sender address change.

Our teams are actively working to complete these migrations and minimize further impact. We will provide further updates as needed.