Codat incident
Sage 50 Connected Companies unable to fetch data
Codat experienced a critical incident on May 12, 2025 affecting Sage 50 and Sage 50, lasting 6h 15m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 12, 2025, 10:58 AM UTC
We are actively investigating an issue preventing Sage 50 connected companies from fetching data. Sage50 connected companies should notice that all datasets fail with a FetchError This incident will be updated as soon as we have identified the issue, and no later than 12:57
- identified May 12, 2025, 11:23 AM UTC
We have identified the cause of the incident and are currently implementing a fix to remediate the issue. This incident will be updated as soon as we have successfully tested and rolled out a fix, and no later than 13:30
- investigating May 12, 2025, 12:21 PM UTC
We have identified the cause of the incident and are continuing to implement a fix.
- identified May 12, 2025, 12:21 PM UTC
We have identified the cause of the incident and are continuing to implement a fix.
- monitoring May 12, 2025, 02:20 PM UTC
We have implemented a fix to the problems we had been experiencing with our Sage50 integration. Affected users should now notice that there fetch operations for Sage50 are able to complete without error. Our teams continue to monitor the platform to ensure continued stability. If you experience any issues please contact [email protected] for further assistance.
- resolved May 12, 2025, 05:14 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 fetch data from Sage 50 without error. If you are still affected by this issue, please contact [email protected]