> 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/other/captain-data/common-issues.md).

# Common Issues

## Connection issues

<details>

<summary>My API key is rejected when connecting</summary>

Double-check that you copied the full API key from Captain Data with no trailing spaces. Keys are found in your Captain Data account settings under API access. If the key was recently regenerated, make sure you're using the latest version — old keys are invalidated immediately.

</details>

<details>

<summary>Coupler.io says it can't reach Captain Data</summary>

This usually means Captain Data's API is temporarily unavailable. Wait a few minutes and try running the data flow again. If the issue persists, check Captain Data's status page for any active incidents.

</details>

## Missing data

<details>

<summary>Job Results are empty even though my jobs completed</summary>

Job Results only appear after a job has fully finished processing. If you ran the data flow while a job was still in progress, the results may not have been written yet. Try running again after confirming the job status shows as completed in Captain Data.

</details>

<details>

<summary>I can see jobs but no data in the Job Results entity</summary>

Some workflows are configured to process data without storing explicit result records — for example, workflows that push data directly to an external destination. Check your workflow configuration in Captain Data to confirm it is set to store results.

</details>

<details>

<summary>Only some workflows or jobs appear in the sync</summary>

Coupler.io pulls data scoped to the API key you provided. If your key is tied to a specific workspace, only jobs and workflows within that workspace will be returned. Check whether you need a workspace-level or organization-level API key.

</details>

## Permission errors

<details>

<summary>I get a 403 Forbidden error when syncing</summary>

Your API key may not have sufficient permissions. Captain Data API keys can be scoped — make sure the key has read access to the entities you're trying to pull (workflows, jobs, results). Generate a new key with broader permissions if needed.

</details>

## Data discrepancies

<details>

<summary>The record count in Job Results doesn't match what Captain Data shows in the UI</summary>

Captain Data's UI may display aggregate counts that include records from retried or partial job runs. Coupler.io pulls the raw result records as stored by the API, which may differ slightly. Use the Job ID field to cross-reference specific runs if precision is critical.

</details>

## Rate limits

<details>

<summary>My sync fails with a rate limit error</summary>

Captain Data enforces API rate limits that vary by plan. If you're pulling large volumes of job results, try scheduling syncs during off-peak hours or reducing the frequency of runs. If you hit limits consistently, contact Captain Data support about your plan's API quota.

</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/other/captain-data/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.