> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.itential.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server.

# Adapter status is red

> Steps to take when an adapter appears inItential Platform but one of its status indicators is red.

## Issue

The adapter appears inItential Platform but one of the status indicators is red.

## Identify which indicator is red

IAP shows two status indicators for each adapter. If the **first indicator** is red, the adapter did not come up — follow the steps in [Adapter not inItential Platform](./adapter-not-in-iap). If the **second indicator** is red, the adapter is running but the health check is failing.

## What to check for a failing health check

**Verify connectivity.** The adapter must be able to reach the external system. See [Connectivity](./connectivity).

**Verify the health check path.** The default health check path is often a placeholder that does not correspond to a real endpoint on the external system. If this is the case, the health check will always fail until you configure a valid path in `/adapter-home-dir/entities/.system/action.json`.

**Verify authentication is configured correctly.** See [Authentication](./authentication).

**Enable debug logging.** Debug logs are essential for understanding exactly what the adapter is sending and receiving. Enable debug-level logging inItential Platform Admin Essentials for the adapter, then review the logs.

To isolate the health check specifically, configure the integration test to run only the health check against the real system (update `sampleProperties.json` with live connectivity details and set the log level in `package.json`), then run the integration tests with debug logging enabled.

**Test the health check call independently.** Run the equivalent request in Postman or with curl to get a baseline for what a successful response looks like. Compare this to what the adapter is sending.

If the logs do not identify the cause, contact the Itential Adapters Team with the log output.