Skip to Content

Known issues in Jitterbit private API gateways

Introduction

This page documents known issues that have been identified with recent versions of private API gateways. For known issues that have been identified with other Jitterbit Harmony applications, see Known issues.

11.30 and earlier

  • API gateway self-test utility fails

    • Summary: The command line self-test utility fails with the message Failure, test call to API failed.

    • Additional Information: This error may be due to missing required fields within the API created by the self-test utility.

    • Workaround: To resolve the issue, upgrade to private API gateway version 11.31 or later.

      With earlier versions, you can add the required fields and re-run the test:

      1. Open the API configuration for the API named ApiGatewayTest.
      2. In step 2, populate the Service Name field with any value, such as service, and the Path with /.
      3. Save and publish the API.
      4. Re-run the self-test utility.

      If the test is still unsuccessful, it may be failing due to another reason.