Resolved -
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 push and pull data from and to Xero as expected.
If you are still affected by this issue, please contact support@codat.io
Jul 28, 16:56 BST
Update -
We are continuing to work with our partner Xero, and a resolution has been identified. Both parties are looking to assuage the problem asap and a resolution should be implemented as soon as possible.
As per our observations, the failures are intermittent, so any push or pull operations which don't succeed as expected can be retried. As soon as we are confident that a fix has been deployed, we will update the status page to reflect this.
Jul 28, 10:55 BST
Identified -
We are continuing to work with our partners at Xero in an attempt to mitigate this issue.
As per our observations, the failures are intermittent, so any push or pull operations which don't succeed as expected can be retried. As soon as we are confident that a fix has been deployed, we will update the status page to reflect this.
Jul 28, 09:13 BST
Update -
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 the fix, which will be no later than 13:25
Jul 24, 12:25 BST
Update -
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 12:48 UK Time
Jul 24, 11:48 BST
Investigating -
Following on from Incident https://status.codat.io/incidents/92vdwfbdrw97, we are still observing some Xero failures.
Affected users will notice that their push or pull operations to Xero are failing with an Auth - related error. The errors appear to be transient, so our users are advised to retry any failed operations.
This incident will be updated as soon as we have identified the issue, and no later than 11:55
Jul 24, 10:55 BST