Troubleshooting Inbound SOAP Web Services in Qntrl | Qntrl Online Help

Troubleshooting

1. Cannot create Inbound soap   

  1. Missing required fields: Ensure Name, URI, and Authentication Type are provided.
  2. Duplicate URI: Use a unique URI for each request.

2. Cannot receive incoming SOAP requests   

  1. Incorrect endpoint URL: Ensure clients are calling the correct Qntrl endpoint.
  2. Firewall restrictions: Allow inbound requests through the firewall.
  3. Authentication failure: Ensure proper authentication credentials are provided.
 

3. SOAP message not processing correctly   

  1. Incorrect XML format: Ensure the request body is well-formed XML and follows the standard SOAP structure.
  2. Missing required parameters: Check the API documentation for mandatory fields.
  3. Request method mismatch:
    1. Use GET requests only for fetching the WSDL.
    2. Use POST requests for sending SOAP messages.
  4. Invalid body format: The request body must contain a valid SOAP XML payload in raw format.
 

4. Request fails due to validation error       

  1. Missing mandatory parameters: Ensure all required parameters are included in the request.
  2. Incorrect parameter format: Match the data types (e.g., number, text) and allowed values.
  3. Regex or length mismatch: Input may not meet defined pattern or length constraints.
  4. WSDL Compliance Enabled: the operation name in the request must exactly match the one defined in the WSDL. Otherwise, the request will be rejected.  

5. WSDL contract not loading   

  1. Syntax errors: Ensure the WSDL XML structure is valid and correctly formatted.
  2. Network issues: If fetching the WSDL externally, check internet connectivity.
 

6. Rate limit errors       

  1. Too many requests (429 Error): The request rate has exceeded the defined limit.
  2. Wrong policy attached: Confirm the correct rate limit policy is selected.
  3. Per-IP not working as expected: Review whether the Per-IP option is enabled as needed.

7. Function error debugging

  1. Check script logs: Review the logs for any errors or issues in the script execution.
 

8. Authentication errors   

  1. Incorrect credentials: Verify the provided credentials match the expected authentication method.
  2. Expired tokens: If using token-based authentication, refresh or regenerate tokens.

Best practices  

  • Use Postman, CURL or Qntrl's Outbound SOAP Web Service to test the endpoint during development.
  • If using OAuth, ensure the correct scope is set and token is valid.
  • Always test each endpoint before publishing.

    • Related Articles

    • Bridge Troubleshooting FAQs

      1. Prerequisites & System Requirements 1.1 What are the prerequisites for installing and using Qntrl Bridge? Before installing Qntrl Bridge, ensure the following prerequisites are met: Administrative (Windows) or sudo (Linux/macOS) privileges are ...

    • Troubleshooting

      1. WSDL URL fetch failure Invalid WSDL URL: Verify the WSDL URL and ensure it is accessible. Test the URL in a browser. Authentication required: If authentication is needed, provide the correct credentials. 2. Cannot modify WSDL contract Downloaded ...

    • Troubleshooting

      1. Cannot create inbound REST module Missing required fields: Ensure Name, Base URI, and Authentication Type are provided. Duplicate base URI: Use a unique base URI for each module. Invalid base URI format: The base URI should begin with a / and ...

    • Troubleshooting

      1. Cannot execute API Make sure all required fields are filled in correctly — this includes the URL, query parameters, headers, and request body. Missing or incorrect values can prevent the API from executing successfully. 2. Unauthorized or ...

    • Troubleshooting FAQ

      1. Why is my WebSocket not connecting? Check if the endpoint URL is correct Verify the Authentication Type(OAuth/API Key) Ensure the connection is not blocked by network/firewall 2. Why are messages not being processed? Verify the Resource Selection ...