MuleSoft · Salesforce Connector
SALESFORCE:CONNECTIVITY
Short answer
SALESFORCE:CONNECTIVITY means a connection to Salesforce could not be established. Review the connector configuration and the reconnection strategy.
VerifiedLast verified
01Error text
Error type: SALESFORCE:CONNECTIVITY02Likely causes
- A problem occurred and a connection could not be established.
03How to fix it
- Review the Salesforce connector configuration, including the credentials and URLs it uses.
- Review the reconnection strategy on the configuration.
- For TLS problems, add the VM argument
-M-Djavax.net.debug=sslwhile troubleshooting. It affects performance, so remove it afterward. - 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:CONNECTIVITY.
04Official documentation
→Related errors
- SALESFORCE:RETRY_EXHAUSTEDSALESFORCE:RETRY_EXHAUSTED means the maximum number of retries for the Salesforce operation was reached. Fix the error that each attempt hit, which is logged before this one.
- SALESFORCE:MUTUAL_AUTHENTICATION_FAILEDSALESFORCE:MUTUAL_AUTHENTICATION_FAILED means mutual TLS authentication with Salesforce failed. Check the certificate and key the connector presents, using SSL debug logging to see the handshake.
- SALESFORCE:COMMUNICATIONSALESFORCE:COMMUNICATION means a communication error occurred between the Mule app and Salesforce. Read the full exception to find which call failed and why.
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