Amplience experienced a minor incident on June 30, 2026 affecting DAM, lasting 2h 31m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 30, 2026, 02:02 PM UTC
We are aware that a subset of legacy processing jobs are experiencing intermittent issues. We have identified the cause and are working to restore normal service. We will provide further updates as progress continues.
- resolved Jun 30, 2026, 04:34 PM UTC
We have successfully implemented a fix.
- postmortem Jul 02, 2026, 12:47 PM UTC
**Incident Start Time** 9 June 2026, 00:00 UTC **Incident End Time** 30 June 2026, 17:37 UTC **Issue Summary** A small number of legacy Processing Jobs intermittently failed to run at their scheduled times. As a result, some automated asset processing tasks, such as set creation and metadata updates, were not completed as expected. **Root Cause** The issue was caused by a planned authentication change introduced by Bitbucket as part of the retirement of its app password authentication method. During scheduled transition periods, authentication requests using the deprecated method were temporarily rejected, preventing some Processing Jobs from downloading the scripts required to execute. **Corrective Actions** We have implemented a permanent fix to remove the dependency on the deprecated authentication method. As a result, these Processing Jobs are no longer affected by Bitbucket's scheduled transition periods. We have identified all Processing Jobs impacted during the incident and are replaying them where appropriate to ensure the expected processing is completed. If you have any questions or believe your workflows require additional review, please contact our Support team at [support.amplience.com](http://support.amplience.com).