On Thursday, August 30 at 09:46 EST \(13:46 UTC\), the Studio Professional team observed API failures during a release rollback procedure. These failures caused disruptions for some of our studio customer applications.
### Incident Details
After a scheduled release was completed for Studio Professional, it was observed that client applications were not behaving as expected with certain theming elements being applied incorrectly. To avoid further corrupting of layout data, a decision to rollback the release was taken. During the rollback, Studio Professional API failed to respond which led to unavailability of Studio Professional Portal, CMS metadata APIs and Studio Professional Client Applications. This was an unexpected effect of one of the database sub-systems temporarily going offline.
### Resolution Details
At 10:13 EST \(14:13 UTC\), the rollback was complete, all systems and related data were available again in its original state prior to the release.
### Mitigation & Planned Actions
The Studio Professional team is investigating alternative future rollback procedures that would lead to minimal disruption of client applications who consume Studio Professional. In addition, the team will look at adding client side caching to improve overall availability of client applications during situations like these.
Performance and stability are our team's top concerns and we'll continue to work in these areas for our users.
We apologize for the inconvenience this may have caused. Thank you for your understanding and support.