Maintenance codes.

What this means: Emma could not validate a member or account action from Salesforce.

Common causes: Invalid email; Emma rejected the request; connected Emma user lacks access.

What to do: Confirm email and required fields, check the Emma connection, then retry. Guide: Audience Members.

What this means: Updating the Salesforce email opt-out or opt-in field on Contact or Lead failed.

Common causes: Validation rules; missing field access on HasOptedOutOfEmail; triggers blocking save.

What to do: Try saving the Contact or Lead manually to see validation errors, then fix and retry. Guide: Audience Members.

What this means: Updating Contact or Lead fields while importing Emma audience details failed.

Common causes: Validation rules; picklist mismatches; wrong field types; bad Salesforce Id in Emma custom fields.

What to do: Read the Maintenance message. Fix the Salesforce save error, then re-run sync or import. Guide: Creating Records.

What this means: A field mapping uses a Salesforce object or relationship Emma does not support.

Common causes: Unsupported parent object; invalid relationship path.

What to do: Remove or change the unsupported mapping in Field Mappings. Guide: Field Mappings.

What this means: Import Wizard could not create a Salesforce scheduled job for the run-as user.

Common causes: User already has too many scheduled jobs.

What to do: Remove unused scheduled jobs for that user, or run the import as another user. Guide: Import Wizard.

What this means: Importing Emma statistics into Salesforce failed.

Common causes: Emma maintenance; network issue; transient save error.

What to do: Usually recovers on the next sync. Check Maintenance if it repeats. Guide: Manage General Settings.

What this means: Updating Salesforce with Emma subscriber statistics failed.

Common causes: Emma maintenance; network issue; transient save error.

What to do: Usually recovers on the next sync. Check Maintenance if it repeats. Guide: Manage General Settings.

What this means: Salesforce storage is full, so Emma sync or import cannot save records.

Common causes: Org data or file storage limit reached.

What to do: Free Salesforce storage or purchase more space, then retry. Guide: Manage General Settings.

What this means: Emma was temporarily unavailable.

Common causes: Emma maintenance; network outage; API downtime.

What to do: Retry later. Contact support if it lasts more than 24 hours. Guide: Troubleshooting.

What this means: A scheduled Import Wizard job was delayed or could not run as planned.

Common causes: Too many scheduled jobs; org queue congestion.

What to do: Space out schedules and confirm the run-as user is still active. Guide: Import Wizard.

What this means: Scheduling or running an Emma sync or import job was delayed or failed.

Common causes: Too many scheduled jobs in the org; colliding Import Wizard schedules.

What to do: Space out Import Wizard jobs and reduce overlapping schedules. Guide: Import Wizard.

What this means: Emma could not check how many sync jobs are currently running.

Common causes: Primary sync user missing Emma Admin; Apex job visibility restricted.

What to do: Assign Emma Admin to the Primary Sync user. Guide: Permissions.

What this means: The Import Wizard report has too many rows. Maximum is 50,000.

Common causes: Unfiltered report; large audience export.

What to do: Add filters to reduce rows, or use a List View or another import source. Guide: Import Wizard.

What this means: Import Wizard could not read row metadata from the Salesforce report.

Common causes: Corrupted or non-tabular report.

What to do: Edit and save the report as Tabular, then retry the import. Guide: Import Wizard.

What this means: Finishing a Report-based Import Wizard job failed.

Common causes: Report errors; save failures at wrap-up; permissions.

What to do: Confirm the report runs correctly in Salesforce, then re-run the import. Guide: Import Wizard.

What this means: The Salesforce report used by Import Wizard looks corrupted or unsupported.

Common causes: Non-tabular report; broken report definition.

What to do: Open the report Id from the message, save it as a Tabular report, then re-run the import. Guide: Import Wizard.

What this means: Bulk updating Emma with custom field mappings failed.

Common causes: Emma temporarily unavailable; same import ran within the past hour.

What to do: Read the Maintenance message. Wait an hour if you just ran a refresh, then try again. Guide: Field Mappings.

What this means: Emma API rate limit was exceeded.

Common causes: Too many sync or import callouts in a short window.

What to do: Wait about an hour, reduce concurrent Import Wizard jobs, then retry. Guide: Troubleshooting.

What this means: Emma could not read Salesforce metadata needed for list views or page layouts.

Common causes: Missing permissions; IP restrictions; metadata access failure.

What to do: Confirm Emma Admin and metadata access for the running user. Guide: Permissions.

What this means: Too many Salesforce batch jobs are already running to start another Emma job.

Common causes: Other packages or Import Wizard jobs saturating the org.

What to do: Usually safe to ignore. Space out imports and retry when the queue is quieter. Guide: Import Wizard.

What this means: Processing a queued Contact or Lead change that syncs to Emma failed.

Common causes: Transient error; permissions; Emma temporarily unavailable.

What to do: Often safe to ignore because the system retries. Check Maintenance if it repeats. Guide: Troubleshooting.

What this means: A Salesforce governor limit was hit while adding or updating Emma members in bulk.

Common causes: Batch size too large; heavy automation; missing permission set.

What to do: Retry with a smaller batch and confirm the user has the Emma permission set. Guide: Import Wizard.

What this means: Cleaning up after an async Emma batch failed.

Common causes: User who started the job lacks abort or cleanup permissions.

What to do: Confirm the run-as user has Emma permissions. The next sync often clears leftovers. Guide: Troubleshooting.

What this means: A Salesforce permissions error blocked an Emma operation.

Common causes: Missing object or field access; missing Emma permission set.

What to do: Review the Maintenance message and grant the required permissions. Guide: Permissions.

What this means: Page layout setup failed due to insufficient privileges.

Common causes: User cannot edit layouts; missing Emma Admin; metadata access blocked.

What to do: Assign correct permissions and retry layout setup. Guide: Permissions.

What this means: Adding Emma related lists to page layouts failed.

Common causes: Insufficient privileges; metadata access; missing Emma permissions.

What to do: Assign Emma Admin and retry page layout setup. Guide: Permissions.

What this means: The current user cannot manage Emma permission sets on the Security screen.

Common causes: Missing access to Permission Sets; not an Emma Admin.

What to do: Use a Salesforce admin or Emma Admin user to open Security settings. Guide: Permissions.

What this means: Import Wizard could not find the Emma account for a List View import.

Common causes: Salesforce not connected to Emma; wrong or missing account selection.

What to do: Reconnect to Emma and confirm the Import Wizard schedule uses a valid Emma account. Guide: Import Wizard.

What this means: Pulling mailing statistics from Emma into Salesforce failed.

Common causes: Temporary Emma or API issue; network outage.

What to do: Usually recovers on the next sync. If it persists, contact support. Guide: Mailing History.

What this means: Calculating open and click rates for mailings failed.

Common causes: Custom triggers conflicting with saves; data inconsistencies; permissions.

What to do: Read the Maintenance message. Check custom automation on mailing objects, then retry. Guide: Mailing History.

What this means: Pulling email tracking history from Emma into Salesforce failed.

Common causes: Temporary Emma or API issue; rate limits; permissions.

What to do: Usually recovers on the next sync. If it persists, contact support. Guide: Mailing History.

What this means: Updating Emma licence details failed.

Common causes: Temporary licensing API issue; network failure; permissions.

What to do: Retry later. Contact support if licence features stay incorrect for more than 24 hours. Guide: Manage Billing.

What this means: The scheduled job that keeps Emma licence details up to date failed.

Common causes: Scheduler permissions; connectivity to Beaufort 12 licensing.

What to do: Confirm Emma Admin is assigned and contact support if licence status stays wrong. Guide: Manage Billing.

What this means: An Emma-related Salesforce Apex job finished with a result that needs review.

Common causes: Failed or aborted sync or refresh; governor limits; callout errors.

What to do: Open Maintenance for the full message. Check Apex Jobs, fix the cause, then retry sync. Guide: Manage General Settings.

What this means: Automatic Emma permission set assignment during install failed.

Common causes: Installer lacked permission-set access; org security restrictions.

What to do: Manually assign Emma permission sets from Emma Settings, Security. Guide: Permissions.

What this means: A Report-based Import Wizard job failed while updating Salesforce records.

Common causes: Save or validation errors; locking; invalid mappings.

What to do: Read the Maintenance message. Fix the report or mappings issue and re-run the import. Guide: Import Wizard.

What this means: Import Wizard could not access the Salesforce report or folder.

Common causes: Missing report or folder access; run-as user lacks permissions.

What to do: Grant the Import Wizard user read access to the report and folder, then retry. Guide: Import Wizard.

What this means: A List View Import Wizard job failed while processing Salesforce records.

Common causes: Empty or invalid mappings; locking issues; save errors.

What to do: Read the Maintenance message. Re-check the List View mappings and retry. Guide: Import Wizard.

What this means: Import Wizard could not load saved field mappings for a schedule.

Common causes: Corrupted mapping data; customised objects or fields; permissions.

What to do: Open the Import Wizard schedule, re-save mappings, and retry. Guide: Import Wizard.

What this means: An Import Wizard job could not start because the Salesforce flex queue is full.

Common causes: Too many Apex jobs already queued or running in the org.

What to do: Wait for other jobs to finish, space out Import Wizard schedules, then retry. Guide: Import Wizard.

What this means: Updating Emma when a Salesforce email address was renamed failed.

Common causes: Email exists on many Emma accounts; API failure; security limits across linked accounts.

What to do: Read the Maintenance message. Confirm the new email in Emma and retry if needed. Guide: Audience Members.

What this means: Disconnecting an Emma account from Salesforce did not complete cleanly.

Common causes: Missing delete permissions; leftover related records; unexpected error mid-disconnect.

What to do: Read the Maintenance message. Confirm the user can delete Emma account records, then retry disconnect. Guide: Installation and Setup.

What this means: Bulk remove or update of group members failed.

Common causes: Import Wizard jobs running too frequently; Salesforce job limits; permissions.

What to do: Space out Import Wizard jobs. Consider Emma Segments for large changes. Guide: Import Wizard.

What this means: Applying custom field mappings between Emma and Salesforce failed.

Common causes: Incompatible field types; missing field-level security.

What to do: Check mapped fields use compatible types and the user can access them. Guide: Field Mappings.

What this means: A field mapping references a Salesforce field that is invalid or unavailable.

Common causes: Field deleted or renamed; wrong object; missing field-level security; unsupported type.

What to do: Review Field Mappings and remove or correct the invalid field. Guide: Field Mappings.

What this means: Creating or updating a Salesforce Contact or Lead from an Emma member failed.

Common causes: Validation rules; picklist mismatches; wrong field types; required fields missing.

What to do: Read the Maintenance message. Fix the Salesforce save error, then retry. Guide: Creating Records.

What this means: Syncing base configuration from Emma to Salesforce failed.

Common causes: Invalid API keys; sandbox connected to a different org; connection error.

What to do: Reconnect to Emma and confirm API keys. Re-run Primary Sync. Guide: Installation and Setup.

What this means: Emma could not read or store package licence details for the current user.

Common causes: Missing Emma Admin; restricted profile; insufficient package licence access.

What to do: Sign in as an Emma Admin user and refresh Billing or licence details. Guide: Manage Billing.

What this means: Adding a Salesforce Contact to Emma failed.

Common causes: Invalid Contact email; Emma API failure; missing field mappings; permissions.

What to do: Read the Maintenance message. Check the Contact email and mappings, then retry. Guide: Audience Members.

What this means: Adding audience members to Emma failed.

Common causes: Invalid email; Emma API failure; group or account permissions; network issue.

What to do: Read the Maintenance message. Confirm the email and Emma account. Retry with a smaller batch. Guide: Audience Members.

What this means: Refreshing Emma groups from the Email Accounts page failed.

Common causes: Emma maintenance or network issue; temporary API failure.

What to do: Read the Maintenance message. Retry the refresh. If it keeps failing, contact support. Guide: Emma Groups.

What this means: Emma connection settings could not be verified.

Common causes: Invalid or missing API keys; Emma account disconnected; network issue.

What to do: Check API keys in Emma Settings and reconnect if needed. Guide: Installation and Setup.

What this means: Creating or updating subscription records in Salesforce failed.

Common causes: Validation rules; duplicate emails; missing required fields; permissions.

What to do: Read the Maintenance message. Fix the Salesforce save error, then re-run sync or import. Guide: Audience Members.

What this means: Updating Emma audience member records in Salesforce failed during sync or import.

Common causes: Validation rules; field type mismatches; record locks; permissions.

What to do: Read the Maintenance message. Review validation rules and field access on Subscription, Contact, and Lead. Guide: Audience Members.

What this means: Adding a Salesforce Lead to Emma failed.

Common causes: Invalid Lead email; Emma API failure; missing field mappings; permissions.

What to do: Read the Maintenance message. Check the Lead email and mappings, then retry. Guide: Audience Members.

What this means: The Salesforce user running Primary Sync does not have the Emma Admin permission set.

Common causes: Sync user changed; permission set removed; restricted profile.

What to do: Assign Emma Admin to the Primary Sync user, then re-run Primary Sync. Guide: Permissions.