Codat incident

QuickBooks Desktop Push Operations not moving beyond Pending

Minor Resolved View vendor source →

Codat experienced a minor incident on April 21, 2026 affecting QuickBooks Desktop and QuickBooks Desktop and 1 more component, lasting 20h 25m. The incident has been resolved; the full update timeline is below.

Started
Apr 21, 2026, 03:59 PM UTC
Resolved
Apr 22, 2026, 12:24 PM UTC
Duration
20h 25m
Detected by Pingoru
Apr 21, 2026, 03:59 PM UTC

Affected components

QuickBooks DesktopQuickBooks DesktopQuickBooks Desktop

Update timeline

  1. investigating Apr 21, 2026, 03:59 PM UTC

    We are actively investigating an issue preventing QuickBooks Desktop Push Operations from completing as quickly as expected. Affected users will notice that a small subset of their QuickBooks Desktop push Operations may take a lot longer than usual to complete, and will appear as though stuck in pending for a long time. This incident will be updated as soon as we have identified the issue, and no later than 18:00

  2. investigating Apr 21, 2026, 04:02 PM UTC

    We are continuing to investigate this issue.

  3. identified Apr 21, 2026, 05:41 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Apr 21, 2026, 06:51 PM UTC

    We have implemented a fix in Production. Affected users should now notice that all Quickbooks Desktop push operations are completing successfully. Please keep in mind that some Push Operations may remain in a Pending status if the end user's computer is offline. These Pending Push operations will resume when they are back online. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact [email protected] for further assistance.

  5. resolved Apr 22, 2026, 12:24 PM UTC

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