One or More Calls Failing

Issue Statement

The adapter is generally working but there is at least one (1) call that is failing.

What You Can Do

Here are some things that you can do to try to resolve the issue:

• Check the unit test. This should tell you if there is an issue in the configuration for that action/call.
• Put the adapter into debug level logging. This is critical to determine what the adapter is doing and be able to compare it to what it is supposed to do.
  • See article on Why Debug Logs Are Important.
  • It might be easier to run integration testing from the adapter with debug logs turned on to test the healthcheck. You need to set up the integration test to just run the healthcheck and to for proper connectivity to the actual system in the sampleProperties.json. Then you will need to set the log level in the package.jsonto see what is happening.- Run the command in Postman or Curl to get a comparison on what works.
  • Focus on the OPTIONS and REQUEST logs to verify the information the other system expects is being sent in the proper format. If the format of the request is not what the other system expects, you may have to change the requestDatatype or the requestSchema.
• You may need to make changes to the action.json and schema within the Endpoint Configuration for the adapter (/adapter-home-dir/entities/specific-entity).
  • action.json: Defines the calls available for the specific entity. The action.json includes things like path, method, data types, schemas, etc.
  • Schemas: Defines the data that will be sent to and returned from the other system.

If you are unable to determine the issue by looking at the log, follow the Support process to create a ticket with the log information and the Itential Adapters Team will be happy to assist.