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 support@codat.io
Posted Sep 04, 2025 - 04:22 BST
Monitoring
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 support@codat.io for further assistance.
Posted Aug 27, 2025 - 19:16 BST
Update
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 support@codat.io for further assistance on reducing the range of the data synced for your affected connections.
Posted Aug 27, 2025 - 16:37 BST
Investigating
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.
Posted Aug 22, 2025 - 12:00 BST
This incident affected: Bill Pay (async) (QuickBooks Desktop), Spend Insights (QuickBooks Desktop), Expenses (QuickBooks Desktop), Legacy - Accounting API (QuickBooks Desktop), and Lending (QuickBooks Desktop).