This incident has been resolved.

We’ve released a hot-fix for this issue that will allow XMIN based incremental syncs to complete successfully when no changes are detected. These changes will be picked up in the next sync, and you can pause/resume a long-running incremental XMIN sync to make sure that you’ve picked up the change. We are monitoring the results after implementing this fix.

Current ETA for releasing the fix is 2pm PDT.

We’ve identified an issue with some XMIN based Postgres connectors not completing incremental syncs. This manifests as unusually long incremental syncs with no updates. We’re currently working on a fix.

Some XMIN based Postgres connectors are not completing incremental syncs. We're investigating the cause of this issue.

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