> ## Documentation Index > Fetch the complete documentation index at: https://docs.sevalla.com/llms.txt > Use this file to discover all available pages before exploring further. # Application Failure > Troubleshoot and resolve issues where your application is unresponsive. In some cases, your application build may succeed, but the application can still fail or time out at runtime. When this happens, Sevalla will display an error on the Application **Overview** page. To find out more information about the issue, click the application health icon. View the application health for an application failure View the application health for an application failure The application health shows you information about when the issue occurred, the error code, and the status of the other processes within the application. Application health Application health If you are still unsure about what is causing the issue, you should also 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.