HTTP Request Timeout

(Eric Johnson) #1

I’m running into an issue where a 3rd party API will occasionally take longer to respond than Flow XO allows. This causes the current flow to fail without feedback to the user. Is there a way to check for a timeout and then let the user know there was an issue? All I see in the logs right now is ESOCKETTIMEDOUT.

(Karen Barker) #2

Hi @hardlyneutral

Unfortunately at the moment we don’t have any form of error handling that would allow you to automatically get back to users in these situations I’m afraid. :disappointed:

There is an idea here on our roadmap that would introduce better error handling methods which you might want to pop over and vote on. :slight_smile:

(Eric Johnson) #3

What about use JS code to query the API? Would that be possible? I haven’t spent too much time digging into how robust the code flows are in the platform.

(Daniel Beckett) #4

Hi @hardlyneutral

It could technically be feasible to find some workaround with the code service if you’re familiar with constructing JavaScript requests. We’re pretty limited in what advice we can offer for custom code though.