Amplience experienced a critical incident on April 30, 2025 affecting Dynamic Content, lasting 22m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 30, 2025, 11:01 AM UTC
We are currently investigating this issue.
- identified Apr 30, 2025, 11:23 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Apr 30, 2025, 11:23 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 30, 2025, 11:23 AM UTC
This incident has been resolved.
- postmortem May 02, 2025, 09:50 AM UTC
**Incident Start Time:** 11:39 BST **Incident End Time:** 12:11 BST **Issue Summary:** On 30th April, users experienced issues where published status changes were not reflected in the UI. This may have appeared as though content was not publishing successfully, despite actual publishing occurring as expected. **Root Cause:** While content was publishing correctly, the issue stemmed from a fault in the event listener responsible for updating the UI with publish status feedback. During a release, an update to the stack misconfigured, resulting in the UI not receiving confirmation of the successful publish. **Corrective Actions:** * Alerts have been implemented to monitor changes made to this specific part of the infrastructure. * We are using this incident to review and strengthen our RBAC \(Role-Based Access Control\) model to prevent similar issues in future. If you have any questions or would like to discuss this further, please reach out to your Customer Success Manager or contact us at [[email protected]](mailto:[email protected]).