Issues with Custom Stream Prefixes and Namespaces

Issues regarding data being written with the expected stream prefixes is actively being investigated.

We’ve identified the root cause of the issue and have stopped syncs from writing to incorrect tables. Our team is now actively working to restore the affected data to the correct, prefixed final tables.

Connection states for impacted connections have been rolled back to a healthy state prior to the issue. Sync jobs after this time will now sync all data to the proper tables, including the data previously synced to the non-prefixed tables. Connections with Source Postgres using CDC will likely need to run a Refresh on the connection to restore it to a healthy state.