> 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/marketing/apify-dataset/common-issues.md).
# Common Issues
## Connection issues
Authentication failed or API token not accepted
Double-check that you copied the full API token from Apify Console under **Settings > Integrations**. Tokens are long strings — make sure there are no trailing spaces or missing characters. If you recently regenerated your token, update it in the Coupler.io source settings.
Data flow connects but returns no data
Confirm that the Dataset ID you entered matches an existing dataset in **Storage > Datasets** in Apify Console. If the actor run failed or produced zero output, the dataset will exist but be empty. Run the actor again in Apify and verify it has items before re-running the data flow.
## Missing data
Only some items are returned, not all
Apify datasets can be very large. Coupler.io paginates through all items automatically, but if you interrupted a run or the actor run itself was incomplete, the dataset may not contain all expected records. Check the `itemCount` field on the Datasets entity to confirm the expected number of items.
Expected fields are missing from item collection output
Item fields are defined by the actor, not by Apify or Coupler.io. If a field you expect isn't showing up, the actor may not have produced it in that run (e.g., a page returned no price data). Check the raw dataset in Apify Console to confirm whether the field exists in the source data.
Website content crawler entity returns fewer fields than expected
The **Item collection website content crawlers** entity uses a fixed set of fields designed for Apify's official website content crawler actors. If you're using a custom or third-party actor that produces different output, use the **Item collections** entity instead to get all raw fields.
## Permission errors
403 Forbidden or "Dataset not found" error
The dataset you're trying to access may belong to a different Apify user or organization. Your API token only grants access to datasets owned by your account. If you're working in a shared Apify organization, make sure you're using a token with the correct organization scope.
## Data discrepancies
Item count in Coupler.io doesn't match Apify Console
Apify reports both `itemCount` (all items) and `cleanItemCount` (deduplicated, non-empty items). Coupler.io exports all items by default. If your destination shows fewer rows than `itemCount`, check whether any items were empty objects — these may be filtered depending on your destination settings.
Data from a previous actor run is still showing up
Each actor run creates a new dataset with a new ID. If your data flow is pointing to the old Dataset ID, it will keep returning data from the old run. After each actor run, update the Dataset ID in your Coupler.io source settings to point to the new dataset.
## Rate limits
Requests are being throttled or failing intermittently
Apify's API enforces rate limits that vary by plan. If you're running multiple data flows pointing to different datasets simultaneously, you may hit these limits. Stagger your data flow schedules or consolidate related datasets using the Append transformation to reduce the number of API calls.
---
# 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/marketing/apify-dataset/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.