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!