"Service Starting Up" Message
If you see a "Service Starting Up" message when using aprity, this is normal behavior and does not indicate a problem.
Why this happens
The aprity backend is hosted on Azure Container Apps with a scale-to-zero configuration. When no requests have been made for a period of time, the backend containers are automatically deallocated. When you make the next request, the containers need to start up again.
This cold start process typically takes 30 to 60 seconds.
What happens automatically
The aprity app handles cold starts transparently:
- Your request is sent to the aprity backend.
- If the backend is starting up, the app displays the "Service Starting Up" message.
- The app automatically retries the request up to 3 times with 10-second intervals.
- Once the backend is ready, the request completes normally.
You do not need to take any action. The app handles the retry process automatically. Simply wait for the operation to complete.
When is this most likely to happen?
You are most likely to see this message:
- First thing in the morning -- If no one has used aprity since the previous day.
- After weekends or holidays -- Extended periods of inactivity cause the backend to scale down.
- After a deployment -- New versions of the backend may trigger a fresh container start.
How long should I wait?
- Normal cold start: 30-60 seconds. The automatic retries handle this.
- Post-deployment start: Up to 2-3 minutes in rare cases.
If the operation has not completed after 3 minutes, try refreshing the page and triggering the action again.
Difference from a service outage
The "Service Starting Up" message is distinct from an error. If the service is truly unavailable due to an outage, you will see a different error message (typically "Service Unavailable" or a callout error). See Callout Errors for that scenario.
Can cold starts be avoided?
On the Enterprise plan, aprity supports always-on configurations that eliminate cold starts. Contact your account manager or support@aprity.ai for details.