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

# Adapter is up but no calls are working

> Steps to take when an adapter is running but all calls are failing.

## Issue

The adapter appears to be running but none of the adapter calls succeed.

## What to check

**Verify the health check is working first.** In some adapters, the health check is set to `none` by default. If that is the case, enable it and confirm it passes. If the health check fails, follow the steps in [Adapter status is red](./adapter-status-is-red) — connectivity and authentication problems at the health check level will affect all calls.

**Check `base_path` and `version`.** If the health check was customized to use a different path than other calls, it may work while everything else fails. Verify that `base_path` and `version` are set correctly for all calls, not just the health check. See [URL paths](./url-paths).

**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 a specific call, configure the integration test to run it against the real system and set the log level in `package.json`.

**Test a call independently.** Run the equivalent request in Postman or with curl to confirm what a successful request and response look like. Compare this to the adapter's behavior in the logs.

**Review the endpoint configuration.** If specific calls need adjustment, changes may be required in the service instance configuration or in `action.json` for the relevant entity at `/adapter-home-dir/entities/<entity-name>`. Be careful not to break the health check or `getToken` when changing shared service instance configuration values.

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

> Steps to take when an adapter is running but all calls are failing.