> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/destinations/categories/ai/gemini/common-issues.md).

# Common Issues

## Connection issues

<details>

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

This usually means the Coupler.io connector isn't active or properly configured in your Gemini CLI session. Check the following:

* Confirm that the Coupler.io connector is set up and enabled in your Gemini CLI configuration.
* Start a **new Gemini CLI session** after confirming the connection — an existing session may not pick up a newly activated connector.

If the connector is active but Gemini CLI still can't access the data, try removing and re-adding the connector configuration.

</details>

<details>

<summary>MCP connector timeouts or data fetch gets stuck</summary>

Intermittent timeouts when Gemini CLI calls the data connector are a known issue with MCP-based integrations. 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 Gemini CLI 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>

## Data issues

<details>

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

A mismatch between the Preview in Coupler.io and the data Gemini CLI 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 Gemini CLI will receive. Always verify the actual row count in Gemini CLI after running the flow. You can also configure a Google Sheets 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 Gemini CLI 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 Gemini CLI, 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>


---

# 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://docs.coupler.io/destinations/categories/ai/gemini/common-issues.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.