> For the complete documentation index, see [llms.txt](https://docs.middle.app/middle-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.middle.app/middle-docs/accounts/health-reports.md). # Health reports Accounts must be configured correctly, but that can be tricky to monitor over the course of time. Connection failures, changes in downstream APIs, unanticipated responses from Workflow actions or syncs, or other issues can occur and result in unsatisfactory performance in an [account](/middle-docs/accounts.md). To help with this, Middle has several validations, or health checks, that it runs on accounts when you navigate to the account page, or run a health report. ## Types of health checks ### Sync coverage This health check looks at all the settings on the account and ensures that syncs have been turned on to match those settings.

This helps catch cases where a workflow has been turned on, but a sync that should pipe data to this workflow has not been turned on. ### Sync failures This health check looks for either recent failures in syncs, or for cases where no records have been returned at all for recent syncs.

This helps catch cases where a sync that was once working might now have invalid credentials, or experienced some other issue preventing data from being gathered. ### Workflow failures This health check looks for recent workflow failures.

Example of a workflow failure validation

This helps catch problems in workflows. Middle users are encouraged to design their workflows to never fail. ## Reporting emails Middle installation [owners](/middle-docs/user-access.md) can turn on daily health reports, which will email a nice summary of all health reports for all installed accounts to all owners.

Health reports setting in Organization settings

--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.middle.app/middle-docs/accounts/health-reports.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.