Integration Hub spoke action failed: spoke returned error response

Authentication credentials are invalid, expired, or missing for the connection used by the spoke action. (high likelihood)

Required input fields for the spoke action are missing, empty, or contain invalid data formats. (high likelihood)

The target system or API endpoint is unavailable, returning HTTP error codes like 500, 503, or timeout errors. (medium likelihood)

Network connectivity issues between the ServiceNow instance and the external system being accessed by the spoke. (medium likelihood)

The spoke action configuration has incorrect endpoint URLs, API versions, or parameter mappings. (low likelihood)

Step 1: Navigate to the failed flow execution in Flow Designer and click on the failed spoke action to examine the output data pill for specific error codes and messages.

Step 2: Check the Connection record used by the spoke action by going to Connections & Credentials > Connections and verify the authentication credentials are valid and not expired.

Step 3: Test the connection by using the Test Connection feature in the Connection record to confirm connectivity to the target system.

Step 4: Review all required input fields for the spoke action and ensure they contain valid data by examining the input data pills and their values in the flow execution details.

Step 5: Check the Integration Hub logs at System Diagnostics > Log > Application Log and filter by source 'IntegrationHub' to find detailed error messages.

Step 6: Verify the target system status and API endpoint availability by checking system status pages or contacting the system administrator.

Step 7: If authentication is confirmed working, re-run the flow with corrected input values or after the target system issues are resolved.

Step 8: Consider adding error handling steps in the flow to gracefully manage spoke action failures and provide meaningful error messages.