Skip to main content
Last updated on

Troubleshoot the HubSpot connector

Beta

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.

Learn how to troubleshoot common issues with the managed HubSpot connector in Lakeflow Connect.

SCOPE error during connection creation or pipeline run​

Error message:

SCOPE Error

Cause:

This error occurs when the HubSpot app is missing required OAuth scopes.

Solution:

Confirm that the connected app in HubSpot has the required OAuth scopes:

  1. Visit the HubSpot app configuration page at https://app-na2.hubspot.com/legacy-apps/<hubspot-id>.
  2. Navigate to your app's Auth settings.
  3. Under Scopes > Required scopes, confirm that all required scopes are selected. For the complete list of required scopes, see Configure OAuth for HubSpot ingestion.
  4. Save any changes and create a new Unity Catalog connection in Databricks.

For app configuration details, see Configure OAuth for HubSpot ingestion.

For connection creation details, see HubSpot.

Pipeline runs slowly​

Symptom:

The pipeline takes a long time to complete, or it appears to be stuck.

Cause:

HubSpot enforces API rate limits, including a 10 second per request limit. When you ingest multiple tables simultaneously, you might hit these rate limits, which slows down the ingestion process.

Additionally, some tables can take a long time to ingest due to high API call requirements. For example, the marketing_campaign_asset table requires 24 separate API calls per campaign. If you have 100 campaigns, you need roughly 2,400 API calls for this single table, compared to roughly 5 API calls for simpler tables. Expect long sync times for these tables. For example, a table with 5,000 campaigns might take roughly four to six hours.

For the full list of applicable tables, see Tables that support batch updates only.

Solution:

To ensure consistent ingestion performance:

  • Limit the number of tables that you ingest at the same time.
  • Split tables across multiple pipelines and schedule them at different times.
  • Monitor your pipeline's progress and adjust your scheduling strategy based on actual sync times.