> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/reference/apps/app-health.md). # App health App Health provides an overview of errors and warnings in your app as well as useful tips to improve performance. With one click, Appfarm Create analyzes your app and generates a list of items for you to review. Run App Health by clicking the heart icon in the toolbar when you're working inside an app.

App health

As shown above, the App Health panel displays the App Size (learn more [here](/reference/apps/app-size.md)). Pin the panel by clicking the pin icon in the top left corner to dock it at the bottom of the window. This lets you keep it open while reviewing and resolving issues. The messages shown in App Health include: * UI components that are always hidden * Required properties that have no value * Functions that don't return a value * Functions with parameters that are not in use * App Variables that are not in use * Data Sources that are not in use * Data Source properties that are not in use * Data Sources that have "Read All Objects" checked * Actions that are not in use * Actions that are empty Use the filter at the top of the panel to select which messages to display. By default, all levels are shown (**All levels**). Select one or more of **Info**, **Warning**, and **Error** to show only those levels, and select **Clear selection** to show all levels again. The App Health panel also lets you resolve issues directly. You can delete UI components that are always hidden, as well as unused Actions and Data Sources, right from the panel. We recommend using App Health actively while developing, and it should be reviewed before deploying to Production. In some cases, the warnings can be ignored, for example, if you must read all objects from a data source, but it's generally advised to address the issues flagged. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.appfarm.io/reference/apps/app-health.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.