Service Graph Connector Connection Troubleshooting Tips and Tricks
Testing IntegrationHub Action via Flow Designer
Testing an IntegrationHub Action via Flow Designer is helpful and will provide more details than the test load 20 records data source does.
To do this, navigate to the flow action and select the Test button in the top right. 
Populate any of the required fields and Run Test. 
Click on "Your test has finished running. View the action execution details".
Expand the action steps and page details to view more details of the error. 
Testing IntegrationHub actions via background script
Testing an IntegrationHub action via background script can be helpful when debugging connection issues. This will allow better visibility into the logs. To do so click on the three dots in the top right of the flow designer action and select Code snippet.
Next, choose Copy Code Snippet to Clipboard.
Navigate to System Definition -> Scripts - Background.
Paste the code snippet you copied.
Remove the wrapping function from the code snippet and populate any input variables.
Select Run script to run the script then examine the output.
Common Connection Issues
Mid Server Issues
A common mid server issue is that most connections filter the mid servers by capability. By default this capability is set to all, which will use all mid servers. Often there is a subset of mid servers that will have access to the system you are trying to connect to. Make sure that a capability is defined for these mid servers, and if not create a new capability and assign it to the correct mid server.
Take the following actions to troubleshoot OAuth connection issues:
- If the integration throws a connection error, the first place to debug a connection issue will be in the Integration Hub/Flow Designer.
- Open the action and click ‘Test’ to test the connection.
- If the connection fails there too, then verify you have entered the correct credentials in the Oauth setup page.
- If all of the above seems to be correct, then the best course of action is to test it in a REST tool like Postman (link below) to see if you can hit the REST endpoint with the credentials that were put in during the guided set up. Performing a test with Postman will prove out that the client credentials are valid.
- If installing an app like Postman is not allowed within your environment, then you can use curl commands to test out the connection locally.
- If the Postman or Curl commands work locally, then the next action could be to test it from the MID Server, if a MID Server is being used in the integration setup. Either install Postman in the MID server or test using the Curl commands to see if you can hit the REST endpoint.
- If the connection works locally and also through MID if MID is being used, then you need to open up a case task to engage the CMDB Integrations team (Assignment Group: App-CMDB-Integrations) for further help.
glide.outbound_http_log.override
When this property is set to true, the property glide.outbound_http_log.override.level determines the log level for all requests and responses. This log level overrides any other log level settings. Only use this property for a limited time when troubleshooting.
- Type: true | false
- Default value: false
- Location: Add to the System Property [sys_properties] table
glide.outbound_http_log.override.level
The log level to use for all requests and responses when glide.outbound_http_log.override is true. Valid values are basic, elevated, and all.
- Type: String
- Default value: basic
- Location: Add to the System Property [sys_properties] table
