For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Open sourceSupportFAQsDocs Home
  • Introduction
    • Overview
    • Retired adapters
      • Overview
      • Result codes
      • Connectivity
      • Authentication
      • Connectivity
      • Dependencies
      • Installation location
      • URL paths
        • Adapter not in Itential Platform
        • Adapter status is red
        • No calls working
        • DEPTH_ZERO_SELF_SIGNED_CERT
        • Wrong response data
        • Wrong request data
        • One or more calls failing
        • Tasks not in Platform
        • Troubleshoot linting and testing
LogoLogo
Open sourceSupportFAQsDocs Home
On this page
  • Issue
  • What to check
TroubleshootSpecific scenarios

One or more calls failing

Was this page helpful?
Previous

Tasks not appearing in Platform

Next
Built with

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.