Amplience incident

Bulk indexing degraded performance

Notice Resolved View vendor source →

Amplience experienced a notice incident on May 29, 2026 affecting DAM, lasting 27m. The incident has been resolved; the full update timeline is below.

Started
May 29, 2026, 10:37 AM UTC
Resolved
May 29, 2026, 11:05 AM UTC
Duration
27m
Detected by Pingoru
May 29, 2026, 10:37 AM UTC

Affected components

DAM

Update timeline

  1. identified May 29, 2026, 10:37 AM UTC

    We have identified the root cause of a known issue and are currently implementing a fix. Further information to follow.

  2. monitoring May 29, 2026, 10:53 AM UTC

    The fix has been deployed and the impact is currently being monitored.

  3. resolved May 29, 2026, 11:05 AM UTC

    We can confirm the fix has been released and validated

  4. postmortem Jun 11, 2026, 01:59 PM UTC

    **Incident Start Time:** 13 May 2026 **Incident End Time:** 29 May 2026 ‌ Between 13 May and 29 May 2026, we identified an issue affecting a subset of assets uploaded through automated workflows, where metadata such as image dimensions, file type, and alt text was not indexed correctly within our search platform. ‌ Assets uploaded manually through the user interface were not impacted. A fix was released on 29 May 2026 to correct the indexing behaviour for newly uploaded assets. ‌ Following the release of the fix, Amplience teams completed a retrospective re-indexing activity for affected assets to restore missing metadata records. ‌ **Root Cause** ‌ The issue was traced to a change introduced in a DAM API release on 13 May 2026, which altered how metadata was written during the indexing process for certain uploaded assets. ‌ **Corrective Actions** ‌ * Increasing validation and review around indexing-related configuration changes * Improving logging and monitoring for metadata indexing processes