Qntrl WebSocket Troubleshooting Guide: Connection, Routing & Message Issues

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 Path is correct (e.g., $.module)

  • Ensure the incoming JSON matches the configured Route Value

  • Check if a Default Route is configured

  

3. Why is my route not getting triggered?   

  • The route value may not match the incoming message

  • JSON path may be incorrect

  • Case sensitivity issues in route values

 

4. Why am I receiving rate limit errors?   

  • The number of messages exceeds the configured policy

  • Update the rate limit in Policy or reduce message frequency

 

5. Why are messages not delivered to a session?   

  • The session might be disconnected

  • Check session status in Session Details

  • Ensure correct session ID or session name is used

 

6. Why is the Connect/Disconnect action not executing?   

  • Ensure Resource Type and Resource are configured

  • Verify the selected function/resource is valid

    • 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 soap Missing required fields: Ensure Name, URI, and Authentication Type are provided. Duplicate URI: Use a unique URI for each request. 2. Cannot receive incoming SOAP requests Incorrect endpoint URL: Ensure clients are ...

    • 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 ...