Update - Sage Intacct team responded that RECORDNO field is now obsolete and removed from API response. In place of RECORDNO field Title or CompanyID could be considered as Primary Key.

We are continuing to work towards a resolution and Fivetran engineering team is currently working on a fix to modify the Primary Key field.

Thank you for your continued patience while we work on fixing this.
Nov 17, 10:59 UTC

Update - We are continuing to work with the Sage Intacct team to understand the root cause of this behavior. In the meantime, we have received confirmation that deselecting the COMPANY table will allow syncs to resume. Once a stable solution is in place, you can re-enable the COMPANY table from the Fivetran Schema tab.
Nov 16, 10:10 UTC

Update - We are continuing to work with the Sage Intacct team to understand the root cause of this behavior. In the meantime, we have received confirmation that deselecting the COMPANY table will allow syncs to resume. Once a stable solution is in place, you can re-enable the COMPANY table from the Fivetran Schema tab.
Nov 16, 01:36 UTC

Update - Engineering team identified that COMPANY endpoint is not receiving RECORDNO field through API response from source and Fivetran considers RECORDNO as a primary key. Missing primary key in API response is causing the PrimaryKeyContainsNull exception.

We are continuing to work with Sage Intacct to understand the possible causes. As a workaround, deselect the COMPANY endpoint on Schema Config to make the connector succeed.

Thank you for your continued patience while we work on fixing this.
Nov 15, 12:39 UTC

Update - We are receiving NULL primary key values from Sage Intacct for the RECORDNO field in the Company endpoint. We are continuing to work with Sage Intacct to resolve the underlying cause of this issue. In the meantime, engineering team is investigating potential workarounds that will mitigate the impact of this incident.
Nov 15, 11:02 UTC

Update - We are continuing to work towards a resolution to this issue. Thank you for your understanding.
Nov 15, 03:30 UTC

Update - We are still trying to identify potential workarounds for customers impacted by this issue while simultaneously working with Sage Intacct's Support team. Thank you for your continued patience.
Nov 14, 03:32 UTC

Update - We are continuing to work with Sage Intacct to resolve the underlying cause of this issue. In the meantime, we are investigating potential workarounds that will mitigate the impact of this incident.
Nov 13, 18:31 UTC

Update - We are receiving NULL primary key values from Sage Intacct for the RECORDNO field in the Company endpoint.
We are in contact with Sage surrounding this issue.
Nov 13, 11:29 UTC

Update - We are continuing to work on a fix for this issue.
Nov 16, 18:46 UTC

Update - Caused by an incident with GCP: https://status.cloud.google.com/incidents/6PM5mNd43NbMqjCZ5REh
Nov 16, 18:19 UTC