Fivetran: Some Hubspot Connection Syncs are failing
Incident
Report for Fivetran
Resolved
This incident has been resolved. We have observed that instance rates are returning to normal levels, and affected connectors are syncing successfully.
Incident Summary
Description:
We identified an issue where the Hubspot connections are failing with "Failed to sync 1 endpoint: - DEAL: Null primary key found while syncing table schema_name.deal. Primary Key dealId is null in the object."
Timeline:
The issue began on 26 January around 04:50:00 AM UTC and was resolved on 26 January around 08:10:00 AM UTC.
Cause:
HubSpot connections were failing due to recent code changes.
Resolution:
The fix was deployed. After deployment, HubSpot connections sync successfully.
Incident Summary
Description:
We identified an issue where the Hubspot connections are failing with "Failed to sync 1 endpoint: - DEAL: Null primary key found while syncing table schema_name.deal. Primary Key dealId is null in the object."
Timeline:
The issue began on 26 January around 04:50:00 AM UTC and was resolved on 26 January around 08:10:00 AM UTC.
Cause:
HubSpot connections were failing due to recent code changes.
Resolution:
The fix was deployed. After deployment, HubSpot connections sync successfully.
Monitoring
A fix has been implemented and we are monitoring the results.
Update
We identified that Hubspot connections are failing with "Failed to sync 1 endpoint: - DEAL: Null primary key found while syncing table schema_name.deal. Primary Key dealId is null in the object."
This was caused by a recent code change. A hotfix is being deployed to resolve the issue.
This was caused by a recent code change. A hotfix is being deployed to resolve the issue.
Identified
The issue has been identified and we are working to resolve it.
This incident affected: Sales connectors (HubSpot).