Common Sync Process Errors and Failures

Sync reports success but no new records transferred

• Reconnect to Constant Contact using the V3 API in Step 2, as the V2 API has been deprecated.

iContact API error 520 during sync

• Error code 520 during sync indicates an issue on the iContact API side, and such errors (any error starting from 500s) are typically resolved by iContact without requiring action from SyncApps users.

Zoho to Constant Contact sync failure

• Records will only sync from Zoho CRM to Constant Contact if they are included in the List View being synced.

Mailchimp to Salesforce campaign sync incomplete

• SyncApps cannot read or write to custom fields that are not included in the Salesforce Task Page Layout. The required field(s), such as Task CazoomiId, must be added to the Task Page Layout, and field-level security must be set to make these fields visible. Without these changes, the sync from Mailchimp to Salesforce campaigns will not complete successfully.
• If the Last Name field is blank in Mailchimp records, the sync to Salesforce will fail unless the feature in Step 1, 'Need to still sync records even if the Last Name field is blank? Select this feature,' is enabled in the SyncApps setup.
• SyncApps requires that the necessary permissions are set in Salesforce, including checking the Marketing User checkbox on the user role, and that field-level permissions are configured as outlined in the Help Center article on Salesforce Permissions Needed For Integration.

Constant Contact API error 413

• Disconnect and reconnect using API v3, as API v2 is no longer working and can cause Constant Contact error 413.

Salesforce to Constant Contact new contact sync failure

• To resolve Salesforce to Constant Contact new contact sync failures, edit your sync profile and authorize SyncApps to connect to Constant Contact in Step 2, ensuring you are using the v3 API.
• If new Salesforce contacts are not syncing to Constant Contact, verify that the contacts are included in the list specified in Step 1 of your SyncApps configuration.
• If the integration is not syncing as expected, ensure that the integration is enabled in your SyncApps dashboard.

Sync not working after API version update

• To resolve the 'No authentication is present' error after the Constant Contact API version update, edit your sync profile and authorize SyncApps to connect to Constant Contact in Step 2 by disconnecting and reconnecting using the v3 API.
• If the integration remains disabled or syncs do not occur after updating to the v3 API, enable any disabled integration to ensure syncs run as expected.