Amplience incident
Unable to add existing node in hierarchy node
Amplience experienced a major incident on July 9, 2024 affecting Dynamic Content, lasting 50m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 09, 2024, 05:29 PM UTC
We have identified a bug during content creation. When selecting "Add existing node" in an existing hierarchy node the message "No content types available" is returned despite valid schema nodes existing on the account
- investigating Jul 09, 2024, 05:33 PM UTC
We are continuing to investigate this issue.
- identified Jul 09, 2024, 05:58 PM UTC
We have identified the issue and are looking to rollback to a working version while the fault is under investigation
- resolved Jul 09, 2024, 06:20 PM UTC
We have rolled back to a working version. This has been tested and we can confirm hierarchies is operational
- postmortem Jul 12, 2024, 02:24 PM UTC
**Issue summary** An incident occurred within Dynamic Content that necessitated an immediate rollback to a previous version. The primary symptom of this incident was observed during content creation: when selecting "Add existing node" in an existing hierarchy node, the message "No content types available" was returned, despite the presence of valid schema nodes on the account. **Root cause** A recent Dynamic Content release introduced a critical bug **Corrective actions** To restore service, we immediately rolled back to a previous version. If you would like to discuss this further, please contact your customer success manager \([[email protected]](mailto:[email protected])\)