> 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/primer-support-review/troubleshooting/audience-wont-sync.md).

# An audience won't sync

Why an audience can't sync to a destination, and how to rerun it after changes.

## It's below the destination's minimum

The most common reason a sync is blocked is that the audience is too small for the destination. Primer shows: *"Recommended audience size for {destination} is >{n} records. Adjust your filters."*

Widen your filters until the estimate clears the destination's minimum — see [Audience size limits](/primer/primer-support-review/audiences/audience-size-limits.md). Remember matching drops records, so build with headroom above the minimum, and note that Meta needs at least 1,500 *matched* records to deliver.

## Rerunning after a change

If you change an audience's filters or add a destination after it's been built, Primer shows a **Rerun** action. Click **Rerun** to rebuild and re-match the audience with the change applied. Until you rerun, the destination keeps the previously built version.

## Still stuck

If the audience reaches [Ready](/primer/primer-support-review/audiences/audience-statuses.md#ready) but a destination still shows no delivery well past the expected [matching time](/primer/primer-support-review/audiences/match-timing.md), or it lands in [Incomplete](/primer/primer-support-review/audiences/audience-statuses.md#incomplete), check the destination connection (see [Fixing a broken connection](/primer/primer-support-review/troubleshooting/fixing-a-connection.md)) and then contact <support@sayprimer.com>.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.sayprimer.com/primer/primer-support-review/troubleshooting/audience-wont-sync.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.