On July 25th, Global Support received multiple reports of unexpected changes in environment order, which disrupted customers’ deployment pipelines and revision numbers. The issue was caused by a backend process that unintentionally triggered environment reordering following renaming actions. Immediate mitigation steps were taken, including pausing the renaming function and correcting affected cases. A long-term solution is being planned, involving improved API controls and a self-service feature.
Posted Jul 29, 2025 - 10:31 UTC
Resolved
We have successfully resolved the issue affecting the order of Non-Production stages for impacted customers in both the Europe (Frankfurt) and US East (N. Virginia) regions. All affected environments are now operating as expected. Thank you for your patience while we worked to restore normal service.
Posted Jul 25, 2025 - 19:45 UTC
Monitoring
We have been able to restore the order of the Non-Production stages for the affected customers. We are now monitoring the results.
Posted Jul 25, 2025 - 16:03 UTC
Update
Customers from US East (N. Virginia) may also be experiencing this issue. Our team is still working on a solution and further updates will be provided once more details are available.
Posted Jul 25, 2025 - 14:54 UTC
Identified
We have identified the cause of this issue. Affected customers may still be experiencing the symptoms already reported.
Our team is actively working on a solution. We will provide an update once more details are available.
Posted Jul 25, 2025 - 13:59 UTC
Investigating
We are aware of an issue affecting staging pipeline in Europe (Frankfurt) region. Tenants with more than one Non-Production stages may be seeing their order reversed. Our team is currently investigating its cause. We will provide an update in as soon as more details are available.
Posted Jul 25, 2025 - 12:22 UTC
This incident affected: ODC - Customer Apps & Data (US East / Virginia, Europe / Frankfurt).