It's also weird because it errors each time but has status 200 (OK)
#HTTP Timeout
plain yarrow
dusk stirrup
On our end, the timeout is 15 minutes, if you are running into anything lower than that, it would be a timeout at the application layer.
plain yarrow
I see, even with keepalive sending it will close after 15 minutes right?
If I switch to websocket, it might fix the stream timeout, do you know if it would still kill the python job when the connection drops too?
And if yes to that, would the only solution be to decouple the job execution from the connection ?
mossy gobletBOT
New reply sent from Central Station thread:
Which http client are you using? Can you try increasing the timeout in the http client you are using?
One more option (but it shouldn't really matter) you can try deploying your service in a different region to see if it change, this shouldn't be the final solution but just a way to get more information
You're seeing this because this thread has been automatically linked to the Central Station thread.
