> For the complete documentation index, see [llms.txt](https://support.sayprimer.com/primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.sayprimer.com/primer/troubleshooting/sync-halted.md).

# A sync halted with an error

What Primer's "Sync halted" messages mean for Meta, Google, Microsoft and LinkedIn, and how to fix each one.

When an ad platform refuses a sync, Primer stops it and shows the platform's reason, starting *"Sync halted:"*. Fix the cause on the ad platform, then run the audience again. Messages that ask you to reconnect are covered in [Fixing a broken connection](https://support.sayprimer.com/primer/troubleshooting/fixing-a-connection.md).

## Meta: "Missing permissions"

Primer's system user isn't an admin of the ad account, so Meta won't let it create or update a Custom Audience there. Fix it one of two ways, then run the audience again:

* **Add the system user as an admin** of that ad account in Meta Business Manager (Business Settings → Accounts → Ad Accounts → the account).
* **Reconnect Meta with a user** that already has admin rights on the ad account.

## Meta: "your admin needs to add this ad account to a business"

Meta only allows Custom Audiences in an ad account that belongs to a business. Ask your Meta admin to add the ad account to your Business Manager, then run the audience again.

## Meta: "Exceeded Meta's 500 custom audience limit"

Meta caps an ad account at 500 Custom Audiences; it's Meta's limit, not Primer's. Delete unused Custom Audiences in Meta's Audience Manager, then retry in Primer.

## Meta: "cannot be edited due to integrity restrictions"

Meta has restricted the audience. Appeal the restriction in Meta, or create a new audience in Primer.

## Google: "EU political advertising declaration"

Google Ads blocks changes to an account whose campaigns lack the EU political advertising declaration. Add the declaration to the campaigns in Google Ads, then try again.

## Microsoft: "rejected the Customer Match terms"

Microsoft won't accept an uploaded list until the account has accepted its Customer Match terms. Accept them in Microsoft Advertising, then run the audience again.

## Microsoft: "belongs to a different ad account"

The audience was created in a different Microsoft Advertising ad account from the one now connected. Reconnect the original ad account, or contact <support@sayprimer.com> to move the audience to the new one.

## "Company audiences can only sync to LinkedIn"

A company audience lists companies rather than people, and only LinkedIn accepts it. Remove the other destinations, or build a people audience for them — see [LinkedIn Ads](https://support.sayprimer.com/primer/connections/integrations/connecting-a-destination/linkedin-ads.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.sayprimer.com/primer/troubleshooting/sync-halted.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
