Amplience incident

Enums not working in content form

Notice Resolved View vendor source →

Amplience experienced a notice incident on January 13, 2025 affecting Dynamic Content, lasting 1h 15m. The incident has been resolved; the full update timeline is below.

Started
Jan 13, 2025, 06:42 PM UTC
Resolved
Jan 13, 2025, 07:58 PM UTC
Duration
1h 15m
Detected by Pingoru
Jan 13, 2025, 06:42 PM UTC

Affected components

Dynamic Content

Update timeline

  1. investigating Jan 13, 2025, 06:42 PM UTC

    We are aware of an issue using enums in the content form screen, we are looking into this and will provide further updates soon.

  2. identified Jan 13, 2025, 07:19 PM UTC

    The issue has been identified and a rollback is being implemented.

  3. monitoring Jan 13, 2025, 07:51 PM UTC

    We have implemented a rollback plan and are currently confirming this has fixed the issue.

  4. resolved Jan 13, 2025, 07:58 PM UTC

    This incident has been resolved.

  5. postmortem Jan 16, 2025, 01:54 PM UTC

    Incident Start Time: 16.11 GMT Incident End Time: 19.55 GMT ‌ **Issue summary** An incident occurred within Dynamic Content that necessitated an immediate rollback to a previous version. The symptom of this incident was observed during content creation, where a schema using enums did not list any values. ‌ **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])\)