3rd Party: QuickBooks connections experienced an issue with the Account endpoint
Incident
Report for Fivetran
Resolved
This incident has been resolved. We paused syncing Account table temporarily. We have confirmed that instance rates have returned to normal, and connections are syncing successfully.
Incident Summary
Description:
We identified an issue with the QuickBooks API, causing repeated API calls and duplicate data for the Account table due to a timestamp filter bug where the LastUpdatedTime field is not updating correctly.
Timeline:
The issue began on 3 November 2025 at 15:07 UTC and was resolved at 4 November 2025 at 09:50 PM UTC
Cause:
A bug in QuickBooks timestamp filter logic is preventing the LastUpdatedTime field from updating, leading to repeated data fetches and redundant API calls.
Impact:
Affects Account table syncs across multiple QuickBooks connectors. Other tables remain unaffected and continue syncing normally.
Connectors may experience rate-limit (429) errors or extended sync durations.
Resolution:
Fivetran has temporarily paused the Account table sync to prevent redundant API calls and avoid rate-limit issues until the issue is fixed at the source.
If your connections continue to experience failures with the 429 error, it may be because your quota has been exhausted. We’re actively working with QuickBooks to resolve this issue and are requesting an API quota refresh for the impacted period (Nov 2–5).
In the meantime, customers encountering 429 errors can contact QuickBooks Support for alternative solutions, such as:
1. Upgrading to the Silver API tier (on the QuickBooks API plan)
2. Requesting an API quota refresh from QuickBooks for the affected period.
We’ll provide an update as soon as we receive confirmation from the QuickBooks Team. Additionally, we will send communications to inform affected customers of the next steps as we receive updates from QuickBooks.
Incident Summary
Description:
We identified an issue with the QuickBooks API, causing repeated API calls and duplicate data for the Account table due to a timestamp filter bug where the LastUpdatedTime field is not updating correctly.
Timeline:
The issue began on 3 November 2025 at 15:07 UTC and was resolved at 4 November 2025 at 09:50 PM UTC
Cause:
A bug in QuickBooks timestamp filter logic is preventing the LastUpdatedTime field from updating, leading to repeated data fetches and redundant API calls.
Impact:
Affects Account table syncs across multiple QuickBooks connectors. Other tables remain unaffected and continue syncing normally.
Connectors may experience rate-limit (429) errors or extended sync durations.
Resolution:
Fivetran has temporarily paused the Account table sync to prevent redundant API calls and avoid rate-limit issues until the issue is fixed at the source.
If your connections continue to experience failures with the 429 error, it may be because your quota has been exhausted. We’re actively working with QuickBooks to resolve this issue and are requesting an API quota refresh for the impacted period (Nov 2–5).
In the meantime, customers encountering 429 errors can contact QuickBooks Support for alternative solutions, such as:
1. Upgrading to the Silver API tier (on the QuickBooks API plan)
2. Requesting an API quota refresh from QuickBooks for the affected period.
We’ll provide an update as soon as we receive confirmation from the QuickBooks Team. Additionally, we will send communications to inform affected customers of the next steps as we receive updates from QuickBooks.