@kapa.ai On the Hubspot Source Connector to BigQuery I get “978 records extracted”, but “no records loaded” why is that ? I am on HubSpot v6.5.5 , BigQuery v2.10.2, Airbyte 2.0.1

The knowledge sources do not explicitly cover your exact combination of connector versions (

source-hubspot

6.5.5,

destination-bigquery

2.10.2, and Airbyte 2.0.1) for this specific record count. However, based on common HubSpot-to-BigQuery sync behaviors in Airbyte, here are the most common reasons why records are extracted but not loaded: 1. The Attempt or Stream Execution Died Early (False Success) In some cases, a sync job's read attempt extracts records into memory or buffer, but fails or terminates unexpectedly before the batch is committed to the destination. Due to job orchestration bugs or missing retries, the overall sync can be reported as "succeeded" while showing

records_emitted > 0

and

records_committed = 0

/ "no records loaded" [Sync job marked]. 2. Typing & Deduplication / Normalization Failures If you are using destinations with Typings & Deduplications (or normalization): • Schema mismatch / Malformed data: HubSpot objects often contain invalid formats (such as bad timestamps, unexpected null/control characters, or invalid date values) that fail during BigQuery loading or SQL transformation stages [Source Hubspot 0.1.53; destination-bigquery When using]. • Query / Merge complexity: If your HubSpot instance has a very large number of custom properties, the generated destination merge/typing queries can fail or time out during the load/transform step [source-hubSpot to BigQuery]. 3. BigQuery Authentication or Upload Timeout During batch or resumable upload calls to BigQuery, credential expiration (e.g.,

400 Bad Request: Request had invalid euc header

or

Invalid credential

) can cause BigQuery load jobs to fail silently or stall, preventing buffered records from being committed to the final table [Forum Post: Bigquery; destination-bigquery Sync stuck]. Recommended Troubleshooting Steps: 1. Inspect the Full Sync Logs: ◦ Look closely at the

destination

worker logs around the end of the sync to check for BigQuery API errors (e.g.,

400 Bad Request

,

INVALID_ARGUMENT

, or SQL execution failures) [Forum Post: Bigquery; destination-bigquery Sync stuck]. ◦ Check if the raw table (in the

airbyte_internal

dataset) contains records with loaded timestamps or errors [BigqueryDataDumper.kt; BaseSqlGeneratorIntegrationTest.kt]. 1. Upgrade Connector Versions: ◦ Consider updating

destination-bigquery

to a newer version (v3.x+), which supports Direct Load and resolves many long-query and loading issues [destination-bigquery When using; source-hubSpot to BigQuery]. ◦ Update

source-hubspot

to the latest version (e.g., v6.7.1+) to ensure you have the latest fixes for pagination and API response handling [fix(source-hubspot) continue CRM]. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help., with interactive elements