Codat incident

QuickBooks Desktop: Some larger datasets are failing with Fetch Errors

Minor Resolved View vendor source →

Codat experienced a minor incident on August 22, 2025 affecting QuickBooks Desktop and QuickBooks Desktop and 1 more component, lasting 12d 16h. The incident has been resolved; the full update timeline is below.

Started
Aug 22, 2025, 11:00 AM UTC
Resolved
Sep 04, 2025, 03:22 AM UTC
Duration
12d 16h
Detected by Pingoru
Aug 22, 2025, 11:00 AM UTC

Affected components

QuickBooks DesktopQuickBooks DesktopQuickBooks DesktopQuickBooks DesktopQuickBooks Desktop

Update timeline

  1. investigating Aug 25, 2025, 06:51 PM UTC

    We are actively investigating an issue which is intermittently affecting datasets from QuickBooks Desktop companies. Affected users will notice that some datasets fail with a FetchError. This is usually when the dataset is slightly larger in size than average.

  2. investigating Aug 27, 2025, 03:37 PM UTC

    We are still actively investigating this issue. Affected clients will notice that their QuickBooks Desktop connections are unable to complete a read sync (pull operation) in Production for some datasets. Datasets affected will typically return a status of 'fetchError'. While we are still looking into this issue, as a partial workaround, we recommend clients to reduce the range of data synced for affected connections. Please contact [email protected] for further assistance on reducing the range of the data synced for your affected connections.

  3. monitoring Aug 27, 2025, 06:16 PM UTC

    We have implemented a fix. Affected users should notice that Quickbooks Desktop syncs have returned to normal. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues, please contact [email protected] for further assistance.

  4. resolved Sep 04, 2025, 03:22 AM UTC

    The incident has now been resolved, ongoing monitoring has shown the Quickbooks Desktop platform has returned to normal stability. All users previously affected should be able to pull data without disruption. If you are still affected by this issue, please contact [email protected]