MuleSoft · HTTP Connector
HTTP:SERVICE_UNAVAILABLE
Short answer
HTTP:SERVICE_UNAVAILABLE means the server could not handle the request because it is down for maintenance or overloaded (HTTP 503). The fault is on the remote side, so retry after a delay and handle the error if the service stays down.
VerifiedLast verified
01Error text
Error type: HTTP:SERVICE_UNAVAILABLE02Likely causes
- The server is unable to manage the request because it is down for maintenance or overloaded.
- HTTP Connector treats any status code from 500 through 599 as a failure and raises an error.
03How to fix it
- Check the status of the remote service. This error is raised by the response it sent, not by your Mule app.
- If the service is overloaded by your own traffic, reduce it by setting
maxConcurrencyon the calling flow. - Retry after a delay: wrap the request in an Until Successful scope and set
maxRetriesandmillisBetweenRetries. - Handle the failure with an error handler of type
HTTP:SERVICE_UNAVAILABLEfor the case where every retry fails.
04Official documentation
→Related errors
- HTTP:INTERNAL_SERVER_ERRORHTTP:INTERNAL_SERVER_ERROR means the server hit a situation that prevented it from fulfilling the request the HTTP Request operation sent (HTTP 500). Read the response body and the remote system's logs to find what failed there.
- HTTP:TOO_MANY_REQUESTSHTTP:TOO_MANY_REQUESTS means the server received too many requests from your app in a given amount of time (HTTP 429). Send fewer calls at once and retry after a delay.
- MULE:RETRY_EXHAUSTEDMULE:RETRY_EXHAUSTED means every retry of an execution block failed, most often an Until Successful scope whose final retry did not succeed. Fix the error that the processors inside the scope keep raising, or adjust maxRetries and millisBetweenRetries.
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