> 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/ms_copilot_studio/common-issues.md).

# Common Issues

## Connection issues

<details>

<summary>The agent doesn't call the Coupler.io tool</summary>

If your agent ignores the Coupler.io tool or says it can't access the data, check the following:

* Confirm **generative orchestration** is turned on for the agent — without it, the agent won't decide to call MCP tools on its own.
* Verify the tool was added under **Tools → Add a tool → New tool → Model Context Protocol** with the correct Coupler.io MCP server URL.
* Make sure at least one data flow with the **Microsoft Copilot Studio** destination has completed a successful run.

</details>

<details>

<summary>Authentication or consent fails when using the tool</summary>

The Coupler.io MCP tool uses **OAuth 2.0** with **Dynamic discovery**, so Copilot Studio registers itself automatically — you don't add a client ID or secret. If sign-in fails:

* Confirm the tool's authentication is set to **OAuth 2.0** with **Dynamic discovery**, not a manual client ID/secret setup.
* When the consent card appears in chat, sign in to Coupler.io to authorize the tool. Each user signs in once.

{% hint style="warning" %}
If you re-created the tool or changed its authentication settings, users may need to sign in again through a fresh consent card.
{% endhint %}

</details>

<details>

<summary>The agent can't see a data flow I just created</summary>

Only data flows that use the **Microsoft Copilot Studio** destination are available to the agent. If a data flow uses a different destination, the agent won't see it. Confirm the destination and that the flow has completed a successful run.

</details>

## Data issues

<details>

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

A mismatch between the Preview in Coupler.io and the data the agent receives can occur when the same identifier appears multiple times and deduplication affects the export differently than the preview.

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

If 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 Microsoft Copilot Studio 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 Microsoft Copilot Studio, 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/ms_copilot_studio/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.