We have resolved this incident.
Jun 17, 15:50 UTC
We have released a fix to temporarily skip the sync of the "overpayment" table if there are any errors returned for it.
We are waiting for Xero support to reply on the resolution of the root cause of this issue. Following the resolution, we will remove the temporary table skip.
Jun 17, 15:09 UTC
Some connectors are failing with an error containing "Primary Key overpaymentID is null in object".
This is caused by the Xero API incorrectly returning the OverpaymentId values as null. The Xero documentation informs that this should be a unique value: https://developer.xero.com/documentation/api/accounting/overpayments#get-overpayments
We are seeing this get resolved by itself for some customers and we are in the process of reaching out to Xero Support to resolve this.
Jun 17, 13:09 UTC
The issue has been identified and we are working to resolve it.
Jun 17, 08:00 UTC