> 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/fixing-a-connection.md).

# Fixing a broken connection

What the Reconnect and Missing permissions banners mean and how to fix a failed data source or destination connection.

When a data source or ad destination connection fails, it's marked **Failed** on the **Connections** page, with a banner saying what's needed. Audiences that use it show a **Connection error** banner pointing you back to it.

## "Action required: Reconnect your account"

Primer's authorization on the platform is no longer valid — most often because:

* The access token expired or was revoked.
* The account's password changed, invalidating the session.
* Someone removed Primer's access on the platform's side.

To fix it:

1. On the **Connections** page, find the connection showing the banner.
2. Click **Reconnect {service}** and log back in to the platform.
3. Re-approve Primer's access.

## Salesforce: "API permissions are disabled for this user"

Salesforce won't let the connecting user use its API, so Primer can't connect. Ask your Salesforce admin to give that user the permission described in [Salesforce](https://support.sayprimer.com/primer/connections/integrations/connecting-a-crm/salesforce.md), then connect again.

## "Action required: Missing permissions"

The connected user can't do what Primer needs in the ad account — for example, create audiences. Fix the user's access on the ad platform (or reconnect with a user who has it), then retry. [A sync halted with an error](https://support.sayprimer.com/primer/troubleshooting/sync-halted.md) covers each platform's message.

## Still failing

If a connection stays **Failed** after reconnecting, 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 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/fixing-a-connection.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.
