# Common Issues

## Connection issues

<details>

<summary>API token not accepted or connection fails</summary>

Make sure you're using your **personal API token**, not an OAuth token or a team token. Find it in ClickUp under your avatar → **Settings** → **Apps** → Personal API Token. Copy the full token without any extra spaces.

If the connection still fails, try regenerating the token in ClickUp and entering the new one in Coupler.io.

</details>

<details>

<summary>Data flow runs but returns no data</summary>

This usually means your API token doesn't have access to the spaces or tasks you're trying to export. ClickUp respects workspace permissions — if you're not a member of a space or it's set to private, those items won't appear.

Check that the ClickUp account associated with your token has the correct access level. If a workspace owner set up the token but the data lives in a space shared only with other members, you'll need a token from a user with access to that space.

</details>

## Missing data

<details>

<summary>Closed or completed tasks are missing</summary>

By default, closed tasks are excluded from the export. Go to the **Advanced settings** step in your data flow and enable **Include closed tasks**.

</details>

<details>

<summary>Lists entity shows only metadata, not tasks</summary>

This is expected behavior. The **Lists** entity returns list-level metadata (name, ID, status) — not the individual tasks inside. To get task data, add the **Tasks** entity to your data flow.

</details>

<details>

<summary>Deactivated users don't appear in time tracking data</summary>

ClickUp's API does not return time entries for deactivated users, even for dates when they were active. This is a ClickUp API limitation and cannot be worked around through Coupler.io settings.

</details>

<details>

<summary>Custom fields are missing from the export</summary>

Custom fields are available through the **List Custom Fields** and **Team Custom Fields** entities. Add one of these entities to your data flow. For task-level custom field values, they should also appear as separate columns in the Tasks export — if they're missing, try re-running the data flow after adding the relevant custom fields entity.

</details>

## Data discrepancies

<details>

<summary>Fewer rows than expected — data appears truncated</summary>

Enabling too many entities in a single data flow can cause API calls to fail or time out, resulting in partial data. If you're seeing fewer rows than expected, try splitting your entities across separate data flows rather than running them all at once.

Very large workspaces (tens of thousands of tasks) may also hit processing limits. Adding filters or splitting by space can help.

</details>

<details>

<summary>Time tracking totals don't match ClickUp's built-in reports</summary>

ClickUp's API does not return time entries for deactivated users (see above). If your ClickUp reports include historical time from users who have since been deactivated, the totals will differ. Also check that you're converting milliseconds to hours correctly — divide the `duration` field by 3,600,000.

</details>

## Rate limits

<details>

<summary>Sync fails with timeout or rate limit errors</summary>

ClickUp's API has rate limits that apply per token. Running many entities simultaneously (Tasks, Time Trackings, Users, Custom Fields, etc.) can trigger rate limit errors or timeouts.

{% hint style="warning" %}
If you're running more than 4–5 entities in one data flow, consider splitting them into separate data flows and staggering their schedules to avoid hitting API limits.
{% endhint %}

</details>