Zephyr Scale Outage History

The cause of this incident was an issue in the frontend deployment that affected the ability to access the Test Cycle edit view. This resulted in the view failing to load correctly, though the underlying data and backend systems were not impacted. We want to reassure customers that **no data was lost** during this incident. All Test Cycle data remained safe and intact throughout. During our investigation, we identified the faulty deployment as the root cause and rolled out a fix to restore normal functionality. Test Cycle edit view access has been confirmed as working. **If you are still experiencing issues**, please clear your browser cache and perform a hard reload of the tab, as cached frontend assets may need to be refreshed. While we are working hard to deliver the best experience to our customers, we apologise for any inconvenience that this might have caused.

The issue has been caused by an error with the Forge platform, logged by Atlassian on their StatusPage: [https://jira-software.status.atlassian.com/incidents/c436c8y239dv](https://jira-software.status.atlassian.com/incidents/c436c8y239dv) With Forge not processing scheduled tiggers properly, Zephyr can’t refresh authorization tokens for tenants. This has not impacted all tenants, but about 300-400 tenants were still impacted. After the issue was fixed with Atlassian, it took a long time for all authorization tokens to be refreshed for Zephyr. We are following up with Atlassian to check why it has taken so long, and what can be done in the future to minimize the impact for Forge apps. We apologise any inconvenience.