Contact Us 1-800-596-4880
  1. Homepage
  2. Salesforce Marketing Cloud Connector (4.0)

  3. Troubleshooting Salesforce Marketing Cloud Connector

All Connectors

Troubleshooting Salesforce Marketing Cloud Connector 4.0 - Mule 4

To troubleshoot Anypoint Connector for Salesforce Marketing Cloud (Salesforce Marketing Cloud Connector), become familiar with the information about interpreting commonly thrown exception messages.

Enable SSL Logging

Enable SSL logs to investigate an issue related to TLS communications.

Set your SSL log level depending on your required level of detail:

  1. Enable only SSL log details:

    javax.net.debug=ssl

  2. Enable only handshaking details. (The handshake protocol is a series of messages exchanged over the record protocol.)

    javax.net.debug=ssl:handshake

  3. Enable handshaking details and SSL details at the same time:

    javax.net.debug=ssl, handshake

  4. Enable the dumping of all details and traffic data:

    javax.net.debug=all

    This option is very verbose and under normal circumstances is not necessary.
SSL logging results in a performance impact for HTTPS or other TLS connections. Enable SSL logging only to troubleshoot a specific issue and do not enable it for extended periods. SSL logging produces a significant amount of log messages and can inundate your log file if it is left enabled and unattended.

To enable SSL logs:

Set the debug parameter as an argument in the runtime configuration for the application.

  1. In Studio, right-click on the project and select Run > Run Configurations.

  2. Go to the Arguments tab and add -M-Djavax.net.debug=ssl in the VM arguments section.

Enable Verbose Exception Logging

Enable verbose exception logs to show a complete stack trace of the error instead of the default truncated output:

  1. In Studio, right-click on the project and select Run > Run Configurations.

  2. Go to the Arguments tab and append the arguments in the VM arguments section to add the mule.verbose.exceptions property. For example:

    -XX:PermSize=128M -XX:MaxPermSize=256M -Dmule.verbose.exceptions=true

Enable Verbose Logging

To get a better understanding of why an application’s interaction with Salesforce Marketing Cloud Connector is failing, temporarily enable verbose logging for the connector.

Remember to always disable enhanced verbosity after troubleshooting, because it can affect your Mule application’s performance.

To enable verbose logging in the configuration file:

  1. Access Anypoint Studio and navigate to the Package Explorer view.

  2. Open your application’s project name.

  3. Open the src/main/resources folder.

  4. Open the log4j2.xml file inside the folder.

  5. Add an <AsyncLogger> tag inside the <Loggers> tag:

    			<Loggers>
				...
				<AsyncLogger name="com.mulesoft.connectors.salesforce.marketing" level="DEBUG"/>
				...
			</Loggers>

  6. Save your application changes.

  7. Click the project name in Package Explorer and then click Run > Run As > Mule Application.

Understand Commonly Thrown Exceptions

Here is a list of commonly thrown exception messages and how to interpret them:

  • SFDC-MARKETING-CLOUD:CONNECTIVITY

    Either a connection could not be established or there is a connectivity error.

  • SFDC-MARKETING-CLOUD:ERROR_RESPONSE

    The external service responds with an error.

  • SFDC-MARKETING-CLOUD:INVALID_INPUT

    The provided input data for an operation is not valid.

  • SFDC-MARKETING-CLOUD:PARSING

    An error occurs when parsing the input or output data to XML.

  • SFDC-MARKETING-CLOUD:RETRY_EXHAUSTED

    The maximum number of retries for the operation is reached.

  • SFDC-MARKETING-CLOUD:THROTTLED

    The external service throttles the API calls since the API calls cause slow system performance.

See Also

Back to top
View on GitHub