MuleSoft · Salesforce Connector
SALESFORCE:NOT_FOUND
Short answer
SALESFORCE:NOT_FOUND means Salesforce could not find the requested resource. Check the ID or name the operation sends.
VerifiedLast verified
01Error text
Error type: SALESFORCE:NOT_FOUND02Likely causes
- The server could not find the requested resource.
03How to fix it
- Log the identifier or resource name the failing operation uses and confirm it exists in the org the app is connected to.
- 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:NOT_FOUND.
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.
- 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.
- HTTP:NOT_FOUNDHTTP:NOT_FOUND means the HTTP Request operation received a 404 response because the server could not find the requested resource. Check the URL shown in the error description, then correct the request or handle the error type in an error handler.
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