Fivetran incident

Fivetran: HubSpot Connections Failing with NullPointerException for email_campaign

Resolved after 3 hours 54 minutes, affecting HubSpot, on March 3, 2026.

resolved Mar 03, 2026, 10:20 PM UTC

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 impacting Hubspot connections, which resulted in syncs failing with the following error: "Failed to sync 1 endpoint(s) with error: {email_campaign=java.lang.NullPointerException: Cannot invoke <>" Timeline: This issue began on 2026-03-03 at 18:00 UTC and was resolved on 2026-02-25 at 22:00 UTC. Cause: This was determined to be caused by a change in connector sync behavior. Resolution: The changes to the sync strategy have been reverted and connections are now syncing successfully.

Started
Mar 03, 2026, 06:25 PM UTC
Resolved
Mar 03, 2026, 10:20 PM UTC
Duration
3h 54m
Detected by Pingoru
Mar 03, 2026, 06:25 PM UTC

Affected components

HubSpot

Update timeline

  1. identified Mar 03, 2026, 06:25 PM UTC

    The issue has been identified and we are working to resolve it.

  2. identified Mar 03, 2026, 07:52 PM UTC

    We have identified the root cause of the issue: recent changes to the HubSpot connector introduced a NullPointerException in the email_campaign object, resulting in sync failures, and we are actively working on a hotfix to resolve it.

  3. monitoring Mar 03, 2026, 10:05 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 03, 2026, 10:20 PM UTC

    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 impacting Hubspot connections, which resulted in syncs failing with the following error: "Failed to sync 1 endpoint(s) with error: {email_campaign=java.lang.NullPointerException: Cannot invoke <>" Timeline: This issue began on 2026-03-03 at 18:00 UTC and was resolved on 2026-02-25 at 22:00 UTC. Cause: This was determined to be caused by a change in connector sync behavior. Resolution: The changes to the sync strategy have been reverted and connections are now syncing successfully.

Your product runs on more than Fivetran

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →