MuleSoft · HTTP Connector

HTTP:GATEWAY_TIMEOUT

Short answer

HTTP:GATEWAY_TIMEOUT means a server acting as a gateway or proxy did not receive a response from its upstream within the specified time (HTTP 504). The timeout happened behind the gateway, not in your Mule app's own Response Timeout.

VerifiedLast verified

01Error text

MuleSoft error
Error type: HTTP:GATEWAY_TIMEOUT

02Likely causes

  • The server acting as a gateway or proxy to manage the request did not receive a response within the specified time.
  • HTTP Connector treats any status code from 500 through 599 as a failure and raises an error.

03How to fix it

  1. Find out which upstream service is slow, and what timeout the gateway or proxy applies.
  2. Reduce the work the request triggers, or have the gateway's timeout raised by its owner.
  3. If a retry is safe, wrap the request in an Until Successful scope and set maxRetries and millisBetweenRetries.
  4. Handle the failure with an error handler of type HTTP:GATEWAY_TIMEOUT.

iNotes

HTTP:TIMEOUT is the different error raised when your own request times out waiting for a response.

04Official documentation

Test every fix in a non-production environment before you apply it to production. See how entries are verified.

More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.