Troubleshoot REST/SOAP Integration Hub Steps - Support and Troubleshooting

Troubleshoot REST/SOAP Integration Hub Steps Issue Use this procedure to troubleshoot errors in REST or SOAP steps in Integration Hub, especially when you need to investigate the HTTP status code, request body, response body, or error message returned by the integration.

Release .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Any supported release

Resolution 1. Enable outbound HTTP logging Integration Hub REST/SOAP steps use outbound HTTP calls. You can enable HTTP logging globally to capture additional information about these requests.

Configure the following system properties:

glide.outbound_http_log.override glide.outbound_http_log.override.level Important: These properties affect outbound HTTP logging globally. You cannot configure a different HTTP log level for an individual REST step.

Enable the required logging level only for the duration needed to troubleshoot the issue, and reduce or disable verbose logging after troubleshooting is complete.

2. Reproduce the integration error After configuring the required logging:

Execute the Integration Hub flow or action that contains the REST/SOAP step. Reproduce the error. Review the outbound HTTP logs. Check the HTTP status code and response details returned by the endpoint. Use the response information to determine whether the issue is related to authentication, request data, endpoint availability, or the remote system.

3. Capture REST step output for debugging You can expose response information from the REST step so that it can be used by subsequent actions in the flow.

To make the output available as data pills:

Configure the Post Message action to include the required REST output values. Include relevant values such as: Request body HTTP status code Response body Error message Save the action. In the next action, open the data pill selector. Locate the outputs under Post a message. Select the required output variable. These values can then be used for troubleshooting, logging, notifications, or conditional logic.

4. Use the response to identify the cause Use the HTTP status code together with the response body to determine the likely cause.

Status code Typical indication What to check 400 Bad request Request body, required fields, data format 401 Authentication failure Credentials, authentication profile, token 403 Access denied User permissions, API permissions, authorization 404 Resource not found Endpoint URL, resource/path, record identifier 408 Request timeout Endpoint response time and network connectivity 429 Too many requests API rate limits or throttling 500 Server-side error Remote application/server logs and response body 502/503/504 Gateway/service availability issue Remote service availability, gateway, timeout configuration The status code alone may not identify the root cause. Always review the response body and error message when available.