Some Recharge connectors are failing

This incident has been resolved. We have observed that instance rates have returned to normal levels and affected Connections are syncing successfully.

We have applied a fix to resolve the issue by disabling webhook events for the SUBSCRIPTION and SUBSCRIPTION_HISTORY tables temporarily. We will continue to monitor all affected connectors until they resume their normal sync functionality.

As a temporary workaround please disable the subscription_history table in the connector schema tab. This will allow other endpoints to continue to replicate while we work on a solution.

We started observing the new error "Invalid Root Entities found" causing sync failure. Our Engineering team continue to work towards resolving the issue.

We have applied a fix to resolve the behavior causing the Recharge connectors to fail. We will continue to monitor all affected connectors until they resume their normal sync functionality.

We have identified an issue with our Recharge connectors, where syncs are failing due to an issue that occurs when data is ingested from the charge endpoint. We will continue to investigate and provide additional updates.

As a temporary workaround, please disable your Charge table in the connector schema tab. This will allow other endpoints to continue to replicate while we work on a solution.

The issue has been identified and we are working to resolve it.