> 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/sources/category/files-and-tables/coda/common-issues.md).

# Common Issues

## Connection issues

<details>

<summary>Invalid API key error when connecting</summary>

Double-check that you copied the full API key from **Coda Account settings → API settings**. API keys in Coda start with `4a6f...` and are long strings — partial copies are a common cause of auth failures. Also confirm that the key hasn't been revoked or regenerated since you last used it.

</details>

<details>

<summary>Connection succeeds but no data appears</summary>

This usually means the API key belongs to a Coda account that doesn't own or have access to the docs you're trying to pull. Make sure the API key is from the account that has read access to the relevant docs and tables.

</details>

## Missing data

<details>

<summary>Rows entity returns no results</summary>

The Rows entity requires a specific doc ID and table ID. If either is missing or incorrect, the sync will return empty. Verify both IDs in the Coda URL — the doc ID appears after `/d/` and the table ID after `#` in the browser address bar.

</details>

<details>

<summary>Some columns are missing from the Rows export</summary>

Coda returns row values as nested key-value pairs using column IDs, not display names. If certain columns aren't appearing, check whether those columns exist in the specific table view you're syncing — hidden columns in a view may not be returned by the API.

</details>

<details>

<summary>Sync tables show up in Tables entity but have no rows</summary>

Sync tables in Coda pull data from external sources and may not always be fully populated. If the external sync hasn't run recently in Coda, the rows won't be available via the API either. Trigger a sync refresh in Coda first, then re-run your Coupler.io data flow.

</details>

## Permission errors

<details>

<summary>403 Forbidden when accessing a specific doc</summary>

The API key you're using belongs to a user who doesn't have access to that doc. In Coda, access is per-doc — being an admin on one doc doesn't grant access to others. Ask the doc owner to share it with your account, then re-run the data flow.

</details>

## Data discrepancies

<details>

<summary>Row counts in Coupler.io don't match what I see in Coda</summary>

Coda may return paginated results and very large tables can be truncated if API rate limits are hit during a sync. Check whether filtered views are being used — the Rows entity respects the default view, which may exclude some rows. Try syncing from the source table rather than a filtered view.

</details>

## Rate limits

<details>

<summary>Sync fails or times out on large tables</summary>

Coda's API has rate limits that can slow down or interrupt syncs for tables with thousands of rows. If you're hitting this consistently, try splitting large tables into multiple data flows or scheduling syncs during off-peak hours to reduce the chance of collisions with other API activity.

</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/sources/category/files-and-tables/coda/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.
