As you know, AppSheet experienced service disruptions on April 28th, 2026, primarily affecting users in Asia and Europe. The incident was triggered by a bug in a deployment made the previous day, which allowed infinite cycles to execute during app automations. This led to a continuous increase in CPU and memory consumption, eventually causing internal server errors and high latency across the global service for approximately 4 hours. Users specifically utilizing the APAC and EU data residency zones (DRZs) were not affected.
The root cause was traced back to a code change intended to prevent stack overflow errors during consistency checks. While it successfully stopped those specific errors, it inadvertently permitted automations with circular dependencies to run, creating resource-intensive loops. The global service was stabilized through a combination of rolling back to a previous stable build and carefully routing regional traffic to restore system health.
We appreciate your patience as our team worked to thoroughly investigate the incident and validate the safeguards we are putting in place to prevent this from happening in the future.
Isn’t it possible to roll out AppSheet server deployments exclusively to free users first? They used to handle deployments this way, which added significant value to having a paid license.
I suspect that it has become difficult now because they need to update the core platform architecture itself, rather than releasing updates on a feature-by-feature basis like they used to.
However, since there are so many apps running in production environments globally, I strongly hope they will reintroduce a verification phase using free accounts, just like before.
Nothing has changed in terms of how AppSheet is rolled out. Certain types of changes can be put behind feature gates and rolled out slowly (to free users first and then later paid users). Other types of changes require a full server update. This is always how it has been, and we still put changes behind feature gates that are rolled out slowly when we can and when it makes sense to do so. Sometimes engineers just make mistakes and create bugs that turn into outages.