MuleSoft · Salesforce Connector
SALESFORCE:LIMIT_EXCEEDED
Short answer
SALESFORCE:LIMIT_EXCEEDED means the operation went over a specific Salesforce limit. A documented example is creating more than 200 entities at once with the Create operation, so split the records into smaller batches.
VerifiedLast verified
01Error text
Error type: SALESFORCE:LIMIT_EXCEEDED02Likely causes
- A specific limit is exceeded, for example by trying to create more than 200 entities at once with the Create operation.
- The docs also say you need to know the rate limits that apply to your org.
03How to fix it
- Find which limit was hit from the error description.
- For Create, send 200 records or fewer per call by splitting the input into batches.
- Turn on verbose logging: in
log4j2.xmladd<AsyncLogger name="org.mule.extension.salesforce" level="DEBUG"/>inside<Loggers>. Turn it off after troubleshooting. - Handle the failure with an error handler of type
SALESFORCE:LIMIT_EXCEEDED.
04Official documentation
→Related errors
- SALESFORCE:INVALID_INPUTSALESFORCE:INVALID_INPUT means the input data given to the Salesforce operation is not valid. Compare the payload with what the object accepts, field by field.
- 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.
- SALESFORCE:UNAVAILABLESALESFORCE:UNAVAILABLE means the Salesforce server is unavailable. Retry later, and check the org's status before changing the app.
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