What are the limitations regarding starting and stopping instances of Azure Spring Apps?

Question

Reference information: https://learn.microsoft.com/en-us/azure/spring-apps/how-to-start-stop-service?tabs=azure-portal#limitations The above URL contains the following information: "If an Azure Spring Apps service instance has been stopped or started successfully, you have to wait for at least 30 minutes to start or stop the instance again. However, if your last operation failed, you can try again to start or stop without having to wait.” If you know the reason for these restrictions, please let us know.

Answer 1

@kazuya kurosawa Thanks for reaching out.

The reason for these restrictions is to prevent excessive start and stop operations that can cause instability and affect the performance of the service. When you start or stop an instance, it takes some time for the system to complete the operation and update the status of the instance. If you try to start or stop the instance again before the previous operation is completed, it can cause conflicts and instability in the system. Therefore, to ensure the stability and performance of the service, there is a minimum waiting time of 30 minutes between start and stop operations. There are internal architecture/design/performance/dependent on different azure resources that leads to this limitation.

Please 'Accept Answer' if it helped so that it can help others in the community looking for help on similar topics.