we’re making a call to an outside service. The external service takes half a second to process. However, the error esockettimeout error is occurring. This probably means that the waiting time of the flowxo server to listen for an http request response is short. How to deal with this problem?
In this forum topic (If FlowXO doesn't implement error handling I quit) a solution is given that I did not understand, because regardless the problem is time waiting for the flowxo server.
How to make?
The timeout set on Flow XO’s side for http requests is 30 seconds. Does the request ever succeed or are you getting the esockettimeout every try?
The workaround offered in the mentioned thread will only help if you do sometimes get a successful request.
The basic idea of what Dan suggested in the other thread is that you set an attribute immediately before making the HTTP request and then updated it immediately after the request has completed.
You have a 2nd flow which triggers whenever the attribute is updated to the value you set it to before the HTTP request. The 2nd flow will then wait 35 seconds and then check the value of the attribute. If the attribute is still set to the pre request value then it retriggers the flow with the HTTP request in order to attempt to run the request again.
I hope this helps. 
in the test of our internal call, it spends less than 1 second. I do not understand how this attribute issue will solve this, because when it gives this error, the flow stops. If I try to call again with the same call pattern, it will make a mistake anyway, no?
Hi Kurt,
Do you ever see the request be successful or does it fail every single time you run this? The workaround will only help if the webhook is sometimes successful.