worldline

Documentation

408 - Request Timeout

Description

The server timed out waiting for the request to be completed. This indicates that the client took too long to send the request, or the request processing exceeded the maximum allowed time. The server closed the connection as it was idle for longer than the timeout threshold.

Common Scenarios

  1. Slow network connection : The client's network connection is slow, causing the request transmission to exceed the timeout limit.

  2. Large request payload : The request body is large and takes too long to transmit to the server.

  3. Client processing delay : The client application took too long to prepare and send the request.

  4. Idle connection : The connection was established but no data was sent within the timeout period.

Resolution Steps

  • Increase the timeout duration on the client side to allow more time for request completion.

  • Optimize your request payload by reducing its size where possible.

  • Check your network connection and ensure it is stable and has sufficient bandwidth.

  • Ensure that your client application is not stalling or hanging before sending the request.

  • Retry the request, as temporary network issues may have caused the timeout.

Refer to the API documentation for recommended timeout values and request size guidelines.