We’ve resolved an issue that impacted the availability of the Gadget Web Editor.
Earlier today, we deployed a maintenance job intended to apply to a subset of development environments. Unfortunately, due to a bug, this job triggered a rebuild of all development environments, which overwhelmed our servers and caused them to spike our CPU usage.
As a result, the servers responsible for hosting the Gadget Web Editor were unable to start new workloads. Importantly, the core infrastructure that handles application reads and writes was unaffected, as it runs on a separate set of servers.
To mitigate the issue, we immediately canceled the maintenance job and moved the Web Editor workloads to a dedicated set of servers. This allowed the Gadget Web Editor to recover and will help prevent similar incidents going forward.
As part of our follow up action items we will also investigating additional safeguards to catch issues like this earlier and ensure greater isolation between background jobs and customer-facing services.
Thanks for your patience, and we’re sorry for the disruption.
