> ## Documentation Index > Fetch the complete documentation index at: https://docs.adriel.com/llms.txt > Use this file to discover all available pages before exploring further. # FAQs > Common questions, expected behaviors, and troubleshooting for the HighLevel data source. Answers to common questions about how the HighLevel data source behaves in Adriel, plus workarounds for a few expected limits. ## Why can't I connect my HighLevel account? The HighLevel connector is available only for accounts hosted in the EU or KR server regions. Accounts hosted in other regions, such as US, cannot be connected. If the authorization flow completes but the data source never finishes setting up, the account's server region is the first thing to check. For the full connection walkthrough, see [How to connect HighLevel to Adriel](/data-sources/g-n/highlevel/how-to-connect). ## How do I report on contacts and opportunities together? Each HighLevel data source imports exactly one object type — contacts, opportunities, invoices, forms, calendar events, email campaigns, or phone numbers. To bring several object types from the same HighLevel location into a workspace, create one data source per type from the same authorized location. Once each data source is connected, its widgets can sit side by side on the same dashboard. The available fields for each depend on the object type, so a contacts data source and an opportunities data source expose different columns. ## Why don't I see all my HighLevel records? Each object type imports up to 10,000 records per run (100 pages of 100 records). Locations with more records than that may not be fully represented in a single run. Because HighLevel caches imported rows, coverage builds up across runs as new and changed records are added, but a single very large object type can still exceed what one run captures. Narrowing the reporting to the records that matter — for example by status, pipeline stage, or source — keeps widgets focused on the rows most likely to be present. For the field and breakdown details, see the [HighLevel data reference](/data-sources/g-n/highlevel/data-reference). ## Why are my HighLevel calendar events limited to about seven weeks? Calendar events are fetched for a fixed window that spans roughly the last three days through the next fifty days — about seven weeks centered on the present. The full window is re-imported on every run, so upcoming appointments stay current, but events outside that window are not retained. This behavior is specific to the calendar events object type. Other object types, such as contacts and opportunities, are not bound to this window. ## Why do new columns keep appearing in my HighLevel data? HighLevel imports raw objects rather than a fixed set of metrics, so the column set is discovered from each object type and from the location's own fields. When HighLevel starts returning a field that had not appeared before — including a location's custom fields — that field shows up as a new column on the next sync. The set of available fields and breakdowns can therefore grow over time. Existing widgets keep working; the new columns simply become available to add. ## Why did my HighLevel data source disconnect on its own? A HighLevel authorization can be revoked on the HighLevel side — for example when access is removed for the location or the app is uninstalled. When that happens, Adriel detects it on the next scheduled sync rather than immediately, and the data source is marked as disconnected. Reconnecting through the authorization flow restores it. See [How to connect HighLevel to Adriel](/data-sources/g-n/highlevel/how-to-connect) for the reconnection steps. If the data source repeatedly disconnects even after a fresh reconnection, email `support@adriel.com` with the affected dashboard URL and the HighLevel location. ## Related Fields, breakdowns, refresh cadence, and limits for the HighLevel data source. Authorize a HighLevel location and set up a data source per object type. Recent changes to the HighLevel data source. Another CRM source for deal pipeline and revenue reporting.