Inquiry regarding temporary "App is disabled" error during Builder API deployment
-
We are looking to identify the cause of an "App is disabled." error.
We recently noticed this error logged temporarily in our live service. We want to clarify that we did not explicitly change the app's enable/disable settings at any point.
However, we found that the exact timing of these error logs coincided with when we were deploying to the target app via the Builder API.
We would like to know: is this temporary "disabled" state a known or expected behavior while a deployment is in progress via the Builder API?
Thank you!
-
Hi @moondory77 ,
Yes, you observed correctly.
During the data migration portion of the deployment (which occurs after the system has done a bunch of validation and consistency checks), the system temporarily disables your app to do the actual data migration.
This is to protect the data integrity of your app - as your app's metadata, reference data and cloud code scripts are all changing underneath it. So we disable the app, make the changes, and re-enable the app.
All of this normally takes just a few seconds - though it does depend upon the number of changes being made.
I hope that helps to clarify things!
Paul.
-
[[undefined-ago, M moondory77, ]]
-
@Paul-Winterhalder Thank you for your reply.
To give you more context, we operate three separate app environments: Dev, Staging, and Production.
We frequently execute deployments to the Production environment during live operations, but only after safely completing all tests in Staging. However, every time we do this, the "App is disabled" error occurs temporarily, which in turn causes our custom user scripts to fail.
Experiencing this issue periodically during live operations is negatively impacting our service quality.
Is there any way to prevent this situation? At the very least, is there a specific scope or option within the Deploy API that allows us to push updates without triggering the "App is disabled" state?
