Service Request - Request Timeout

(Sheela Dimayuga) #1

We’ve been testing our Custom Authentication service node, and it would seem that there is a timeout configuration setup (same with any service node types).


Question#1. Is there a way to go beyond the max timeout defined?
Question#2. How do we check/test if the defined timeout has been reached already? We are hoping to display a custom message, instead of getting a “blank” response.

Appreciate your response.

Thank you,

(Subrahmanyam Donepudi) #2

Hi @sheela.dimayuga,
The time out at service node cannot be altered by bot developer beyond the max limit.
However, if you are using an on-premise installation of our platform and could let us know the version of it, I’d could check with our engineering team and get back you on whether we could manage it form platform config files.

Thus said, it would be great if you can let us know the reason why your application cannot POST to the platform’s callback URL within 90 secs. Have you tried sending the request to the callback URL within the time limit 90 secs? If yes, could you let us know if your usecase is achieved?

(Sheela Dimayuga) #3

Thank you @Subrahmanyam! The external authentication page has 2 fields. We were speculating that the user may have fat-fingered a field causing some additional internal validation to occur, thus add more delay. If the chatbot could “maybe” wait further, then that lessens the chances of having to restart with the chatbot convo again.

On the other hand, how can we handle a timeout connection? We have this service node transition setup, but we are not getting the message. Instead, we are only getting a blank response.


(Subrahmanyam Donepudi) #4


Got you. We will discuss this internally and see if we could send provision a timeout message at the service node of type ‘custom authentication’ instead of pushing an empty response. We will keep you posted on the updates.

If webSDK is your preferred channel of communication with the bot, I’d say you could include a logic at webSDK itself to catch the bot response event coming in Web Socket (which is coming empty) and display a different message to the user.

To comment on increasing the timeout at service node, we would need the version of platform you been using at your organisation to check with the development team if the setting can be manageable.