A clear path forward
My app is live but slow or returning timeouts—what should I check?
Check deployment logs and resource use to find what is slowing the app or causing timeouts.
VerifiedRH-0063v2
- Look for repeated timeout or out-of-memory messages in the deployment logs.
- Check the deployment's processor and memory limits. See Monitoring a deployment.
- Open a new Agent chat with recent logs and ask it to find bottlenecks. Remove any secret values from the logs first.
Common causes include database queries without search indexes, operations that block other work, and memory the app fails to release.
With Autoscale deployments, the first request after scaling to zero can take a few seconds. This startup delay is called a cold start.
Did this get you unstuck?
Still stuck?
See what to include and open a support ticket.
Still stuck?
See what to include and open a support ticket.If this page did not solve it, contact Support and describe what you were trying to do and what happened, in your own words. You do not need to gather anything in advance.
Include in your ticket, if you know it
- What you were trying to do
- What happened, in your own words
- What you have already tried, if anything
Copying is optional. No ticket is submitted and no files are attached automatically; send your request in the support form.
Do not include passwords, API keys, or payment-card details.