# Common Issues

## Connection issues

<details>

<summary>Claude can't see my data after the flow runs successfully</summary>

This usually means the Coupler.io extension or connector isn't active in your Claude session. Check the following:

* **Claude Desktop**: Go to **Settings > Extensions** and confirm the Coupler.io extension is toggled on.
* **Claude Web**: Open the Connectors menu and verify that Coupler.io shows as connected.
* Start a **new chat** after confirming the connection — existing chats may not pick up a newly activated extension.

If the extension is active but Claude still can't see the data, try re-authenticating by removing and re-adding the access token.

</details>

<details>

<summary>MCP connector timeouts or the "Get-dataflow" tool gets stuck</summary>

Intermittent timeouts when Claude calls the `Get-dataflow` tool are a known issue with the MCP connector. This can happen when datasets are large or the connection experiences latency.

{% hint style="warning" %}
If you're hitting this frequently, try reducing the amount of data sent to Claude by filtering at the source level in Coupler.io. Sending a focused, smaller dataset is more reliable than sending everything.
{% endhint %}

If the problem persists across multiple sessions, contact Coupler.io support — this may require investigation by the engineering team.

</details>

<details>

<summary>Claude Web connector won't connect — no option to authenticate</summary>

Team and Enterprise Claude accounts require **admin permissions** to add a new connector. If you don't see the option to connect or the button is greyed out, ask your workspace admin to complete the connection or grant you admin access.

</details>

## Data issues

<details>

<summary>Claude sees fewer rows than the Coupler.io preview shows</summary>

A mismatch between the Preview in Coupler.io and the data Claude receives can occur when the same identifier (for example, an `ad_id`) appears multiple times, and deduplication logic affects the export differently than the preview.

{% hint style="danger" %}
Don't rely on the Preview tab alone to confirm what Claude will receive. Always check the actual row count in Claude after running the flow. You can also configure a Google Sheet export to verify that the number of rows is the same and to check what's missing.
{% endhint %}

If you notice specific rows are missing, note the relevant IDs and contact Coupler.io support with the data flow details — this type of discrepancy requires engineering investigation.

</details>

## Permission errors

<details>

<summary>"You've reached your destination limit" or AI usage is restricted</summary>

Coupler.io plans have limits on **destination type**. If you're using Claude as a destination and also sending data elsewhere (for example, Google Sheets), you may hit this limit.

To resolve this, either:

* Remove the other destination and use only Claude, or
* Upgrade to a higher Coupler.io plan that supports multiple destination types.

{% hint style="info" %}
Each active data flow counts toward your plan limits. If you created a test flow with a different destination, delete it to free up your destination slot or upgrade to a higher plan.
{% endhint %}

</details>