Table of Contents
HubSpot enforces a per-portal API rate limit (typically 100 requests per 10 seconds for OAuth apps, plus a daily cap that depends on your HubSpot subscription tier). The connector batches HubSpot reads to stay well under these limits in normal use, but a large first refresh or aggressive scheduled refreshes can push you to the cap.
What you see #
Power BI surfaces the failure as a refresh error. The error body typically includes RATE_LIMITED or 429 Too Many Requests. The connector also writes the error to History → Export History with a one-line reason.
Why it happens #
- Large first sync — a brand-new data source with hundreds of thousands of records can briefly burst against the 10-second window.
- Many parallel refreshes — if several Power BI datasets refresh against the same data source at the same time, the connector multiplies HubSpot reads.
- Daily quota — on smaller HubSpot plans, the daily cap can be hit by repeated full refreshes throughout the day.
How to recover #
- Wait. The 10-second window resets after the failed request; daily caps reset at midnight UTC.
- Re-run the refresh after the window clears.
- Reduce frequency: in Power BI service, drop the refresh schedule from hourly to daily.
- Reduce scope: tick fewer properties on the data source, or add a filter that limits the rows returned.
If you hit limits regularly, it’s worth opening a support ticket. We can look at your portal’s usage pattern and suggest specific tuning (filter recipes, refresh window changes, scope trimming).
