Troubleshoot integrations
Find the message or symptom, see why it happens, and fix it.
How the integrations work is explained in How integrations work. The app still uses the product’s former name in these messages.
Pardot could not be reached. Check the Pardot integration in CAB Settings, then try again.
Section titled “Pardot could not be reached. Check the Pardot integration in CAB Settings, then try again.”Cause
CAB couldn’t connect to Account Engagement, for example because the connection is no longer authorized.
Fix
Check the connection. See Connect Account Engagement.
No active Pardot business unit is assigned to you. Ask your Salesforce admin to assign you to one in CAB Settings.
Section titled “No active Pardot business unit is assigned to you. Ask your Salesforce admin to assign you to one in CAB Settings.”Cause
Lists are added through a business unit, and none is assigned to you.
Fix
Ask your administrator to assign one. See Connect Account Engagement.
The user running the Audience Scheduler (…) is not yet authorized for Pardot. Recurring Pardot Synchronization will not work until the user is authorized.
Section titled “The user running the Audience Scheduler (…) is not yet authorized for Pardot. Recurring Pardot Synchronization will not work until the user is authorized.”Cause
The user who runs the scheduler isn’t authorized for Account Engagement.
Fix
Authorize that user, or run the jobs as a connected user. See Connect Account Engagement and Start the core services.
Scheduled Pardot syncs run as …, who is not connected to Salesforce, so they may fail. Reschedule them under a connected user in CAB settings.
Section titled “Scheduled Pardot syncs run as …, who is not connected to Salesforce, so they may fail. Reschedule them under a connected user in CAB settings.”Cause
The user who runs the scheduled list syncs isn’t connected to Salesforce.
Fix
Run the jobs as a connected user. See Start the core services.
There are more than … members in lists that should be cleansed, which is above the limit for this feature. Cleansing will not be performed as long as this is the case.
Section titled “There are more than … members in lists that should be cleansed, which is above the limit for this feature. Cleansing will not be performed as long as this is the case.”Cause
The lists to cleanse have more members than list cleansing can handle.
Fix
Cleanse fewer or smaller lists. See Limits and requirements.
Marketing Cloud could not be reached. Check the Marketing Cloud integration in CAB Settings, then try again.
Section titled “Marketing Cloud could not be reached. Check the Marketing Cloud integration in CAB Settings, then try again.”Cause
CAB couldn’t connect to Marketing Cloud, for example because the client secret changed or expired.
Fix
Check the connection. See Connect Marketing Cloud.
Your Marketing Cloud client secret has expired. Rotate it in Marketing Cloud and paste the new client secret into Campaign Audience Builder settings to restore the integration.
Section titled “Your Marketing Cloud client secret has expired. Rotate it in Marketing Cloud and paste the new client secret into Campaign Audience Builder settings to restore the integration.”Cause
Client secrets of an installed package in Marketing Cloud expire after a set time.
Fix
Rotate the secret in Marketing Cloud and paste the new one into CAB. See Connect Marketing Cloud and Limits and requirements.
Marketing Cloud did not return the business unit …. The installed package probably cannot see it from its own business unit. Choose another business unit, or create the installed package in your top-level business unit.
Section titled “Marketing Cloud did not return the business unit …. The installed package probably cannot see it from its own business unit. Choose another business unit, or create the installed package in your top-level business unit.”Cause
The installed package can’t see that business unit from its own business unit.
Fix
Choose another business unit, or create the installed package in your top-level business unit. See Connect Marketing Cloud.
A Data Extension addition failed before it sent all its rows, so rows may be missing from the Data Extension. Open the log to see which Data Extension and why.
Section titled “A Data Extension addition failed before it sent all its rows, so rows may be missing from the Data Extension. Open the log to see which Data Extension and why.”Cause
The add failed before it sent all its rows, so rows may be missing.
Fix
Open the log from the notification to see which data extension and why, fix the cause, and add the results again. See Notifications.
This data extension does not have a primary key column. A primary key column is required when adding data via API. Please add such a field to the Data Extension in the Marketing Cloud in order to use it here.
Section titled “This data extension does not have a primary key column. A primary key column is required when adding data via API. Please add such a field to the Data Extension in the Marketing Cloud in order to use it here.”Cause
CAB adds rows through the Marketing Cloud API, which needs a primary key column.
Fix
Add a primary key field to the data extension in Marketing Cloud, or create the data extension in CAB. See Create data extensions.

