Skip to main contentThere may be instances where your application build succeeds, but the application still fails or times out. If this occurs, you should check the following:
Resources
If your application process reaches its memory or CPU limit, it can trigger a restart loop, causing the application to stop responding.
To check this, within your application, click Analytics, select Show limit, and review the Memory usage and CPU usage charts to see if they have reached the limit.
If you have reached the limit, you need to increase the resources for your application. To do this, go to Processes, click the ellipsis (three dots) on your web process, and then click Update process. Select the resource you require for the application and click Update process.
Redeploy the application after updating the resources.
Runtime logs
If your application enters a restart loop due to a runtime error, the Runtime logs will show the cause.
To check these within your application, click Deployments, select the individual deployment, and click Runtime logs.
Identify and fix the error indicated in the logs, then redeploy the application. 
