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

# One or more calls failing

> Steps to take when an adapter is generally working but specific calls are failing.

## Issue

The adapter is working overall but at least one specific call is failing.

## What to check

**Run the unit test for the failing call.** The unit tests can surface configuration issues in `action.json` or schemas that affect a specific action.

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

Focus on the **OPTIONS** and **REQUEST** log entries to verify that the adapter is sending the request in the format the external system expects. If the format is wrong, you may need to adjust `requestDatatype` or `requestSchema`.

**Test the call independently.** Run the equivalent request in Postman or with curl to confirm what a successful request looks like. Use this as a reference when comparing to the adapter's behavior.

**Review the endpoint configuration for the failing call.** The relevant files are in `/adapter-home-dir/entities/<entity-name>`:

* `action.json` — defines the path, method, data types, schema references, and other call-level settings.
* Schema files — define the data sent to and received from the external system.

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

> Steps to take when an adapter is generally working but specific calls are failing.