> 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/time-tracking/clockify/common-issues.md).
# Common Issues
## Connection issues
"NOT FOUND: Request failed with status code 404"
This error typically means your **Workspace ID** is incorrect or doesn't match your API key. Double-check the following:
1. Log in to Clockify and go to **Settings** in the Manage section
2. Copy the Workspace ID directly from the URL (e.g., `https://clockify.me/workspaces/5e450bcf1fffab54e1b0e8e5/settings`)
3. Ensure you're a workspace admin—non-admins cannot access the Settings page
4. Paste the ID exactly as shown, with no extra spaces or characters
5. Verify your API key is still valid (regenerate if unsure)
If the issue persists, regenerate your API key in your Clockify profile settings and try again.
"Request failed with status code 401" or "access token is invalid"
Your API key is invalid, expired, or doesn't match your Workspace ID. Try these steps:
1. Go to [Clockify profile settings](https://clockify.me/user/settings)
2. Scroll to the **API** section at the bottom
3. Click **Generate** to create a new API key
4. Copy the new key and update it in your Coupler.io data flow
5. Run the data flow again
Note: API keys are tied to individual users, not workspaces. If you're the only one using this integration, regenerating your key should resolve the issue.
## Missing data
No data appears after running the data flow
This usually happens when your date range is too narrow or your Clockify workspace has no entries for the specified period. Check:
1. **Verify your date range** — Make sure your start and end dates are correct. The end date must be after the start date.
2. **Check for time entries in Clockify** — Log into Clockify and confirm you have time entries for the date range you specified
3. **Remember the one-month default** — If you set only a start date, Coupler.io pulls one month of data from that date. For example, if you set `2024-11-01` as the start date with no end date, you'll get data through `2024-12-01`
4. **Timezone considerations** — Clockify stores times in UTC. If you have entries near midnight, check your local timezone settings in both Clockify and your destination
If data exists in Clockify but isn't appearing, try running a Summary report first to confirm the connection works, then switch to Detailed or Weekly.
Only partial data is imported (e.g., stops at row 1000)
Large Clockify exports may be truncated due to API response limits. Workarounds:
1. **Narrow your date range** — Split your import into smaller date ranges (e.g., one month at a time) and append them together in your destination
2. **Use Detailed report instead of Summary** — Sometimes one report type is faster than another
3. **Schedule multiple smaller refreshes** — Instead of one large weekly import, schedule daily imports
If you consistently hit limits, contact Coupler.io support for assistance.
## Permission errors
"You must be a workspace admin to access settings"
Only Clockify workspace admins can retrieve the Workspace ID from the Settings page. If you're not an admin:
1. Ask a workspace admin to retrieve the Workspace ID for you (it's in the URL at `clockify.me/workspaces/{WORKSPACE_ID}/settings`)
2. You can generate your own API key from your profile settings, even as a non-admin
Once you have both the Workspace ID and a valid API key, you can create the data flow.
## Data discrepancies
Data looks different in Clockify vs. the imported sheet
Common reasons include:
1. **Time zone differences** — Clockify uses UTC. If your time entries were logged in a different timezone, adjust your local view in Clockify before comparing
2. **Billable status filter** — Summary reports may exclude non-billable entries by default. Check your report settings
3. **Rounding** — Duration may be rounded to the nearest minute or hour depending on your Clockify settings
4. **Running timers** — Time entries that are still "running" (not stopped) may not be included until they're completed
Verify the data in Clockify directly by running a report there, then compare field-by-field with your Coupler.io import.
Date range includes unintended data
Remember: **all times default to 00:00 (midnight)**. If you set an end date of `2024-11-30`, you'll get all data up to `2024-11-30 00:00`. To include the full day, set the end date to `2024-12-01`. Example:
* Start: `2024-11-01` (includes 2024-11-01 00:00 onward)
* End: `2024-12-01` (includes through 2024-11-30 23:59)
This captures the entire month of November.
## Rate limits
"Too many requests" or request throttling errors
Clockify's API has rate limits. If you're running multiple large imports simultaneously:
1. **Stagger your refreshes** — Schedule data flows at different times rather than all at once
2. **Use smaller date ranges** — Break large imports into narrower windows
3. **Reduce refresh frequency** — Decrease the number of daily or hourly scheduled runs
If errors persist after these steps, contact Coupler.io support to review your usage pattern.
---
# 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/time-tracking/clockify/common-issues.md?ask=&goal=
```
`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.