Codat incident

Intermittent API errors

Major Resolved View vendor source →

Codat experienced a major incident on August 24, 2026 affecting Sync For Expenses Connectivity and Sync For Commerce Connectivity and 1 more component, lasting 1h 56m. The incident has been resolved; the full update timeline is below.

Started
Aug 24, 2026, 01:49 PM UTC
Resolved
Aug 24, 2026, 03:46 PM UTC
Duration
1h 56m
Detected by Pingoru
Aug 24, 2026, 01:49 PM UTC

Affected components

Sync For Expenses ConnectivitySync For Commerce ConnectivityCloverCloverSage 50

Update timeline

  1. identified Aug 24, 2026, 01:49 PM UTC

    We're aware of an issue affecting a number of our integrations and sync services and are currently implementing a fix to remediate the issue. Requests to these services are currently returning errors. Retrying will return the same error until we've fixed the issue, so no action is needed from you. Queued syncs will resume automatically once service is restored. All other integrations and services are operating normally. We'll update this page as soon as we have more to share. This incident will be updated as soon as we have successfully tested and rolled out a fix, and no later than 4:00PM GMT.

  2. monitoring Aug 24, 2026, 02:36 PM UTC

    We have implemented a fix. Affected users should now notice that they are again able to use the affected services as normal. Queued syncs will resume automatically. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact [email protected] for further assistance.

  3. resolved Aug 24, 2026, 03:46 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 use affected services without disruption. If you are still affected by this issue, please contact [email protected]