MuleSoft · CloudHub 2.0

504 Gateway Timeout during or after traffic switch to CloudHub 2.0

Short answer

A 504 Gateway Timeout during or after the traffic switch to CloudHub 2.0 means a request ran longer than the load balancer waits. Keep client timeouts under 300 seconds, or raise Read Response Timeout in the private space's Advanced settings.

VerifiedLast verified

01Error text

MuleSoft error
504 Gateway Timeout

02Likely causes

  • The request takes longer than the load balancer's read timeout.

03How to fix it

  1. Keep client timeouts under 300 seconds.
  2. If the API needs longer, raise Read Response Timeout in the private space's Advanced settings. It can go up to 3,600 seconds.
  3. If latency is the cause, increase the replica vCore size or count.

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.