I am not being able to trigger a workflow for a ping http request when it goes into timeout.
I have already tried to implement a trigger on timeout and timeout after retries, both on group and session, without success.
On StreamViewer i see this ERROR: 12002. [ERROR_WINHTTP_TIMEOUT], but when i retrieve the values on the status code and response content parameter I have nothing useful to detect this case.
Any suggestion on what I am missing or a workaround?
Many thanks.
Hi Diogo,
Could you elaborate a bit on what you are trying to achieve? Are you trying to use the slow poll functionality of ping groups (Slow poll mode ping group | DataMiner Docs) or are you implementing the ping group yourself?
Additionally, the trigger for the timeout notification should work when applied to the HTTP session as described on this page Time element | DataMiner Docs
The only scenario I could see where it may not work is if you have something like ignoreTimeout defined.
In that case, a trigger on the session with the option ‘timeout’ or ‘timeout after retries’ should be working for you.
The timeout on session worked after all.. so I was probably doing something wrong before.
Though the timeout after retries on session doesn’t work, which is a problem if retries have been configured for that connection.
Hi Severino,
I’m just doing a regular http session based on a given URL (“http://” + IpAddress + “/ping”).
This http command should work similarly as a ping command for this API.
But from my tests with Postman and accordingly to StreamViewer, it times out as expected when unavailable, though I am not catching this condition on the connector for some reason.
Regards,