MuleSoft · Salesforce Connector
SALESFORCE:INVALID_INPUT
Short answer
SALESFORCE: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.
VerifiedLast verified
01Error text
Error type: SALESFORCE:INVALID_INPUT02Likely causes
- The provided input data for an operation is not valid.
- The docs note that currency values may not exceed 18 characters, and that a value checked against a Salesforce list must be the exact value.
03How to fix it
- Log the input to the failing operation and compare it with the object's fields in Salesforce.
- Correct the mapping that produces the invalid value.
- To see the full stack trace instead of the truncated one, add
-Dmule.verbose.exceptions=trueto the VM arguments. - 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:INVALID_INPUT.
04Official documentation
→Related errors
- SALESFORCE:LIMIT_EXCEEDEDSALESFORCE: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.
- SALESFORCE:INSUFFICIENT_PERMISSIONSSALESFORCE:INSUFFICIENT_PERMISSIONS means the permissions of the connected Salesforce user are not enough for the operation. Grant that user the missing permission in Salesforce, or connect with a user that has it.
- SALESFORCE:INVALID_RESPONSESALESFORCE:INVALID_RESPONSE means the connector could not process the response from Salesforce. Capture the full exception to see what was returned.
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