All Software: Requests Timing Out

If you receive errors indicating that the service has timed out (e.g. HTTP 504 Gateway Timeout, 502 Bad Gateway) there are typically two solutions:

Firstly, check with your IT team to see what the timeout settings are on your corporate proxy. If you're running this workbench during business hours it's possible that you're hitting the timeout on your own proxy server due to network congestion.

Information: SLIP's architecture has set very permissive network timeout limits to enable larger and long-running requests to run without interruption. At the time of writing (July 2017) these are:

- AWS Load Balancer: 10 minutes

- ArcGIS Server Pooling: 10 minutes timeout on requests; 60 seconds for a request to begin sending a response

Secondly, if you've ruled out network timeouts as an issue it may be pay to reduce the size of each request by changing the number of features you're downloading in each request. e.g. If you're currently downloading 75,000 features per request try reducing this to 25,000.

This will help to reduce the likelihood of receiving timeouts due to network congestion and busy servers by increasing the total number of requests you make, but decreasing the size of each request (in terms of data downloaded and data that needs to be handled through our infrastructure). See the tip above Speeding up downloads with larger page sizes (features per request) for more information.

Software-specific Guidance -

- QGIS: WFS Timeout Issues

- All Software: WFS 2.0 Timeouts & Slow Response Times