What this means: The licence check job could not be added to the Salesforce queue.

Common causes: The flex queue is full; too many Apex jobs are already queued or running in the org.

What to do: Usually safe to ignore - the job runs again on the next schedule. Contact support if licence status stays wrong. Guide: Billing.

What this means: Information only. Audit entries record admin actions such as starting a Full sync, refreshing an event, purging data or disconnecting an Eventbrite account.

Common causes: Not an error - one is written every time an admin action is run.

What to do: Nothing. Use the Audit view in Maintenance to see who ran what and when. Guide: Maintenance Codes & Messages.

What this means: An event was found whose Eventbrite account is not connected to Salesforce, so its counts cannot be updated.

Common causes: The Eventbrite account was disconnected; the event belongs to an Eventbrite organisation you have not connected.

What to do: Connect the Eventbrite account from General Settings, or ignore the message if that event is not required. Guide: Installation & Setup.

What this means: Order and attendee counts for one or more events could not be updated.

Common causes: Eventbrite API unavailable or rate limited; validation rules on Eventbrite Event; governor limits.

What to do: Read the Maintenance message. Counts usually correct themselves on the next sync - run a Full sync if they do not. Guide: Events.

What this means: The background job that applies Eventbrite security rules could not run.

Common causes: The running user cannot manage permission sets; org security restrictions; queueable job limits.

What to do: Re-apply security settings as a Salesforce System Administrator. Guide: Permissions.

What this means: The scheduled job that keeps Eventbrite object security up to date could not be created.

Common causes: Too many scheduled Apex jobs in the org; the user cannot schedule Apex.

What to do: Remove unused scheduled jobs, then re-save Security settings. Guide: Permissions.

What this means: An action on the Eventbrite Security settings page failed.

Common causes: Missing access to Permission Sets or Permission Set Assignments; org security restrictions.

What to do: Retry as a Salesforce System Administrator, or assign the Eventbrite permission sets manually in Setup. Guide: Permissions.

What this means: Adding or removing the Eventbrite related lists on page layouts failed.

Common causes: The user cannot edit page layouts; the metadata deployment was rejected; missing Eventbrite Admin.

What to do: Read the Maintenance message, then retry layout setup as a Salesforce System Administrator. Guide: Page Layouts.

What this means: Information only. Your request to add or remove the Eventbrite related lists on page layouts has finished.

Common causes: Not an error - this is logged every time page layout setup completes.

What to do: Nothing. Check the affected layouts if the related lists are not where you expect. Guide: Page Layouts.

What this means: Package licence details could not be read or stored for the current user.

Common causes: Restricted profile; the user cannot see installed package licence records.

What to do: Sign in as a Salesforce admin or Eventbrite Admin user and reload Billing. Guide: Billing.

What this means: Refreshing a single attendee, or the attendee summary shown on a record, failed.

Common causes: The attendee no longer exists in Eventbrite; validation rules or restricted fields on Eventbrite Attendee; an Eventbrite API error.

What to do: Read the Maintenance message, then retry the refresh from the record. Guide: Orders / Attendees.

What this means: The primary sync user does not have the "Eventbrite Admin" permission set.

Common causes: The sync user was changed; the permission set was removed; a restricted profile.

What to do: Assign Eventbrite Admin to the primary sync user, then re-run the sync. Guide: Permissions.

What this means: Event totals such as attendee and order counts could not be calculated.

Common causes: Validation rules or triggers on Eventbrite Event; restricted fields; governor limits on very large events.

What to do: Run a Full sync. If totals stay wrong, contact support with the Maintenance message. Guide: Events.

What this means: The package could not check which Beaufort 12 packages are installed in the org.

Common causes: The running user cannot read installed package details; restricted profile.

What to do: Usually safe to ignore. If features appear missing, reload the page as a Salesforce System Administrator. Guide: Technical Guide.

What this means: Eventbrite was temporarily unavailable when the request was made.

Common causes: Eventbrite maintenance or outage; network failure.

What to do: Wait a few minutes and try again. Check eventbritestatus.com for current outages. Guide: Technical Guide.

What this means: The primary sync schedule could not be created.

Common causes: The org or user already has too many scheduled Apex jobs; the user cannot schedule Apex.

What to do: Remove unused scheduled jobs, then set the schedule again from Sync Settings. Guide: Settings.

What this means: Creating or updating a Lead, Contact, Account or Person Account from an Eventbrite attendee failed.

Common causes: Validation rules, triggers or duplicate rules; required or restricted fields; picklist mismatches; record locks.

What to do: Read the Maintenance message for the record that failed, fix the Salesforce save error, then run a Full sync. Guide: Mappings.

What this means: A page layout deployment did not complete. Current versions of the package log this as EB4SF_PAGE_LAYOUT_ERROR.

Common causes: The user cannot edit page layouts; the metadata deployment was rejected.

What to do: Read the Maintenance message, then retry layout setup as a Salesforce System Administrator. Guide: Page Layouts.

What this means: A Lead, Contact, Account or Person Account rule is switched on, but the Salesforce Matching Rule behind it is missing or inactive.

Common causes: The Matching Rule was deleted or deactivated; it was never activated after setup.

What to do: Activate the matching rules in Salesforce Setup, or turn the rule off in Mappings. Guide: Mappings.

What this means: An internal Salesforce API call made by the package failed.

Common causes: Missing metadata or object access for the running user; IP range or login hour restrictions on the sync user; the session expired.

What to do: Confirm the sync user has the Eventbrite permission sets and is not IP restricted, then retry. Guide: Permissions.

What this means: Eventbrite orders could not be synced into Salesforce.

Common causes: Validation rules or triggers on Eventbrite Order; restricted fields; the Eventbrite account (Org Id) on the order is not connected.

What to do: Read the Maintenance message. Confirm the Eventbrite account is still connected, fix the save error, then run a Full sync. Guide: Orders / Attendees.

What this means: Email activity from Campaign Monitor, Emma or Mailchimp could not be linked to Eventbrite attendees.

Common causes: Validation rules or triggers on the email activity object; restricted fields; the matching attendee record is missing.

What to do: Read the Maintenance message and fix the Salesforce save error, then re-sync. Guide: Emails.

What this means: A Salesforce Opportunity, or its Contact Role, could not be created or updated from an Eventbrite order.

Common causes: Validation rules or triggers on Opportunity; required or restricted fields; missing stage mapping; the Eventbrite event no longer exists in Salesforce.

What to do: Read the Maintenance message, fix the save error, then re-sync the order. Guide: Orders / Attendees.

What this means: Licence and attendee usage details could not be updated.

Common causes: Temporary licensing API or network failure; the user cannot read package licence details.

What to do: Retry later. Contact support if licence features or attendee counts stay wrong for more than 24 hours. Guide: Billing.

What this means: Your user cannot open the Eventbrite Security settings page.

Common causes: No access to the Salesforce PermissionSetAssignment object; restricted profile.

What to do: Open Security settings as a Salesforce System Administrator, or ask an admin to assign the Eventbrite permission sets for you. Guide: Permissions.

What this means: A mapped Salesforce Campaign Member Status could not be created.

Common causes: The Salesforce limit on Campaign Member Statuses has been reached; only the latest 1,000 events are processed per sync; validation rules on Campaign Member Status.

What to do: Remove unused statuses or reduce the number of events being synced, then re-sync. Guide: Events.

What this means: A Default Value on a mapping line is not valid for the Salesforce field it targets.

Common causes: Wrong data type (text into a number or date); a picklist value that does not exist; an unsupported token.

What to do: Open Mappings, correct the Default Value so it matches the field type, save, then re-sync. Guide: Mappings.

What this means: The scheduled job that keeps your Eventbrite for Salesforce licence up to date could not be created during install or upgrade.

Common causes: The installing user cannot schedule Apex; the org already has too many scheduled jobs.

What to do: Remove unused scheduled jobs and reinstall. Contact support if licence status stays wrong. Guide: Billing.

What this means: A sync batch job finished with a failure that is not tied to a single record.

Common causes: Governor limits; the job was aborted; a callout failed part-way through.

What to do: Open Maintenance for the full message, check Apex Jobs in Setup, fix the cause, then run a Full sync. Guide: Settings.

What this means: Syncing Eventbrite events, ticket classes, venues or questions into Salesforce failed.

Common causes: Validation rules or triggers on the Eventbrite objects; restricted fields; a parent (series) event that could not be read from Eventbrite.

What to do: Read the Maintenance message. Fix the Salesforce save error, then run a Full sync. Guide: Events.

What this means: Package licence details could not be read for the current user. Current versions of the package log this as EB4SF_CONFIG_STORED_LICENCE.

Common causes: Restricted profile; the user cannot see installed package licence records.

What to do: Sign in as a Salesforce admin or Eventbrite Admin user and reload Billing. Guide: Billing.

What this means: Base configuration could not be read from Eventbrite.

Common causes: The Eventbrite user does not have the right Eventbrite role; the connection (OAuth token) is no longer valid; Eventbrite API temporarily unavailable; primary sync user missing the "Eventbrite for Salesforce - Full Access" permission set.

What to do: Read the Maintenance message. Reconnect the Eventbrite account from General Settings if the token is invalid, and confirm permissions. Guide: Installation & Setup.

What this means: The event sync could not be started.

Common causes: The Salesforce flex queue is full; too many Apex jobs are already queued or running in the org.

What to do: Wait for other jobs to finish, then start the sync again from Sync Settings. Guide: Settings.

What this means: Salesforce Campaign Members could not be created or updated from Eventbrite attendees.

Common causes: Validation rules, triggers or flows on Campaign Member; the Contact or Lead was never created; restricted fields.

What to do: Read the Maintenance message and fix the save error, then run a Full sync. Guide: Events.

What this means: A billing or subscription action did not complete. Current versions of the package no longer raise this code.

Common causes: Payment details rejected; licence lookup failure; the user cannot view package licence details.

What to do: Retry from Billing. If it repeats, contact support with the Maintenance message. Guide: Billing.

What this means: A Salesforce Campaign could not be created or updated from an Eventbrite event.

Common causes: Sync user missing the Marketing User setting; validation rules on Campaign; required or restricted fields; record type access.

What to do: Enable Marketing User on the primary sync user, read the Maintenance message, then re-sync the event. Guide: Events.

What this means: Eventbrite custom question answers could not be saved to Salesforce.

Common causes: Validation rules, triggers or flows on Contact, Lead or Eventbrite Answer; field-level security; unsupported field types.

What to do: Read the Maintenance message for the record that failed. Fix the Salesforce save error or the mapping, then re-sync answers. Guide: Question & Answers.

What this means: A call to the Eventbrite API did not return a usable response.

Common causes: Eventbrite maintenance or outage; too many requests (rate limiting); network timeout.

What to do: Wait about an hour and try again. Check eventbritestatus.com for current outages. Guide: Technical Guide.

What this means: Syncing Eventbrite attendees, questions or answers into Salesforce failed.

Common causes: Validation rules or triggers on Eventbrite Attendee; field-level security; a missing parent attendee record; governor limits.

What to do: Read the Maintenance message. Fix the Salesforce save error, then run a Full sync. Guide: Orders / Attendees.