Hey there!
Edit: There isn’t a idle timeout anymore.
There is a 60 idle timeout. If no data is received or sent within 60 seconds, the connection will be closed.
This is not well documented (if at all). We could bring that up a bit, but there are other options that might work for you:
Use polling instead of 1 long request. Immediately respond with a 202 (Accepted) HTTP response code and then have your client poll your server every 5 seconds to get the status of your “job”.Send back data through the connection to keep it alive.
The choice of 60s is pretty arbitrary, we could make 120s work! However, if you ever have a job that takes over 120s, then you’re left with the same problem.