> 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/box/common-issues.md).
# Common Issues
## Connection issues
Authentication fails when entering API credentials
Double-check that you're using the **Client ID** and **Client Secret** from a Box app configured with **Client Credentials Grant (CCG)**. Apps using OAuth 2.0 user authentication won't work here. Make sure the app has been authorized by your Box enterprise admin if you're accessing enterprise-level data.
The data flow runs but returns no data
This usually means the User ID is missing or incorrect. The **User ID** field tells Coupler.io which Box account to authenticate as. Verify the ID in your Box developer console under your app's service account details. Without a valid User ID, the connection may succeed but return empty results.
## Missing data
Admin logs or Events entity returns no rows
Admin logs and Events are only available on **Box Enterprise** plans. If your account is on a lower tier, these entities won't return data. Also confirm that your Box app has the `manage_enterprise` or `admin_readwrite` scope enabled — without it, the API call will succeed but return nothing.
Sign requests or Sign templates are empty
Box Sign must be enabled on your account. If your organization hasn't activated Box Sign, these entities will return no data. Check with your Box admin to confirm Sign is part of your subscription.
Trashed items aren't showing up
Trashed items are only visible within Box's retention window — once permanently deleted, they can't be retrieved via the API. If items were purged before your sync ran, they won't appear. Run your data flow more frequently to capture trash contents before purge.
## Permission errors
"Insufficient permissions" error on specific entities
This means the user specified in the **User ID** field doesn't have access to that entity. For admin-only entities like Admin logs, the User ID must belong to a Box co-admin or admin. For file-level entities, the user must have at least viewer access to the relevant content.
{% hint style="warning" %}
Switching to an admin User ID will broaden data access but may expose sensitive audit data. Confirm with your security team before changing this setting.
{% endhint %}
App not authorized for enterprise access
Enterprise-scoped entities require your Box app to be explicitly authorized by a Box enterprise admin in the **Admin Console → Apps → Custom Apps**. If authorization is missing, the API returns a permission error even if credentials are correct.
## Data discrepancies
File counts in Coupler.io don't match what I see in Box
The Box API returns data scoped to the authenticated user. If the User ID belongs to a regular user rather than an admin, only files that user has access to will appear. Switch to an admin-level User ID to get a broader view of all files in the enterprise.
Collaboration roles look different from what's shown in the Box UI
Box uses internal role labels in the API (e.g., `co-owner`, `editor`, `viewer uploader`) that may differ slightly from what's displayed in the Box web interface. These are accurate API values — refer to Box's API documentation for the full role mapping.
## Rate limits
Sync fails or slows down with large numbers of files or events
Box enforces API rate limits per app. If you're syncing large entities like Files or Events across a big enterprise, you may hit these limits. Try splitting your data flow into multiple flows per entity rather than pulling everything at once, and avoid running multiple flows simultaneously.
---
# 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/box/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.