[source-hubspot] Issue: Incremental sync for line_items stalls #53199
Labels
area/connectors
Connector related issues
autoteam
community
needs-triage
team/extensibility
type/bug
Something isn't working
Connector Name
source-hubspot
Connector Version
4.4.9
What step the error happened?
During the sync
Relevant information
Issue Summary
I am experiencing a significant delay when syncing line_items from HubSpot to BigQuery using Airbyte. The process takes an excessive amount of time to start, even though the number of records is small. Logs indicate that the sync remains idle for at least an hour before actually beginning.
Key Observations
Other HubSpot tables sync without issues – This problem is specific to line_items.
Sync hangs before it officially starts – The workload is created and marked as RUNNING, but no actual data transfer occurs for a long time.
The logs repeatedly show idle messages, such as:
Pool queue size: 0, Active threads: 0
This suggests that the process is not actively fetching or writing data.
The buffer remains empty, as indicated by:
Allocated: 10 MB, Used: 0 bytes, percentage Used 0.0
No explicit errors appear in the logs, meaning there is no immediate failure but rather a stall in execution.
hs_bq_line_items_logs.txt
Possible Causes Considered
API rate limits? → Unlikely, since other tables sync fine.
Permissions? → Not an issue, as full refresh works.
Schema-related issues? → There might be a problem with how line_items is processed.
Pagination or cursor (updatedAt) issues? → Airbyte may be stuck waiting for changes.
Questions for Support
Is there a known issue with syncing line_items from HubSpot?
Could this be related to how Airbyte handles incremental syncs on deeply nested or structured data?
Are there specific configurations or workarounds to speed up incremental syncs for this stream?
Logs
I have attached the full logs for further investigation. Let me know if you need additional information.
Thanks for your help! 🚀
Relevant log output
Contribute
The text was updated successfully, but these errors were encountered: