> For the complete documentation index, see [llms.txt](https://docs.acpt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acpt.io/tools/health-check.md).

# Health check

Monitor the health status of the plugin

This tool monitors the health status of the plugin.

<figure><img src="https://3235524095-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fiyf0tSKPgXiyoQ3zV3I6%2Fuploads%2Fgit-blob-daad551a76085cc4dc770bd7d6c2751011f90911%2FHealth-check-%E2%80%B9-Localhost-%E2%80%94-WordPress-11-06-2024_02_30_PM.png?alt=media" alt=""><figcaption></figcaption></figure>

Four checks are performed:

* **Plugin version** — verifies that the plugin version stored in the database matches the installed version
* **DB status** — verifies that the database schema is correct and up to date, and that every ACPT table uses the **InnoDB** storage engine
* **CURL** — verifies that the PHP cURL extension is available, since it's required for outbound requests (license checks, integrations)
* **Cache** — reports whether the ACPT cache is enabled

If one or more checks fail, click the **Run health check** button to attempt an automatic repair.

## InnoDB tables

ACPT's own tables must use the **InnoDB** storage engine. It's the engine that supports transactions (so a failed save is rolled back instead of leaving half-written data) and indexes longer than 1,000 bytes.

Since 2.1.10, ACPT creates its tables as InnoDB even on servers whose default engine is MyISAM, and converts existing ones when you update. If an ACPT table still uses another engine, **DB status** reports "Missing tables or columns, or tables not using the InnoDB engine", and the repair converts it to InnoDB.

### Custom Content Tables

If you use [Custom Content Types](https://docs.acpt.io/custom-content-types/custom-content-types.md), the Health check also lists your own tables that don't use InnoDB, under **Custom Content Tables**:

> These tables don't use InnoDB, so their records don't roll back and foreign keys can't be added: products (MyISAM). Switch them to InnoDB from the Custom Content Tables list.

These tables hold your data, so the repair **never** converts them, and neither does the daily automatic check. Convert each one yourself with the [Switch to InnoDB](https://docs.acpt.io/custom-content-types/tables.md#storage-engine) action in the table list.

[Open a support ticket](https://docs.acpt.io/general/how-to-open-a-ticket.md) if the problem persists.
