Amplience incident

Unable to remove components from Dynamic Content

Minor Resolved View vendor source →

Amplience experienced a minor incident on October 22, 2025 affecting Dynamic Content, lasting 2m. The incident has been resolved; the full update timeline is below.

Started
Oct 22, 2025, 03:06 PM UTC
Resolved
Oct 22, 2025, 03:09 PM UTC
Duration
2m
Detected by Pingoru
Oct 22, 2025, 03:06 PM UTC

Affected components

Dynamic Content

Update timeline

  1. identified Oct 22, 2025, 03:06 PM UTC

    We’ve identified an issue with a recent release that’s impacting content creation. Our team is currently rolling back the affected feature, and we’ll confirm once the rollback is complete

  2. resolved Oct 22, 2025, 03:09 PM UTC

    We can confirm that the affected feature has been rolled back and functionality has returned to normal.

  3. postmortem Oct 28, 2025, 05:00 PM UTC

    **Incident Start Time:** 14:05 BST **Incident End Time:** 16:30 BST ‌ **Issue Summary:** An incident occurred within Dynamic Content that required an immediate rollback to a previous version. The issue presented as users being unable to edit or delete content fields during content creation. ‌ **Root Cause:** The problem was introduced in the latest Content Form Extension release, which modified how form fields and remove actions were rendered and validated. When users attempted to remove a piece of content, no error appeared in the network panel; however, the browser console displayed a “not a function” error. ‌ **Corrective Actions:** * Review and strengthen our testing processes, particularly where cross-functional teams are involved in feature releases. * Ensure validation coverage includes all form and field interaction scenarios before deployment.