Hi everyone, I’m facing an issue with my Airbyte setup. I have a connection from PostgreSQL to BigQuery using CDC. After creating a new table, I added it to the existing publication in Postgres, but Airbyte is not picking up the new table even after a manual sync. Here’s what I’ve done so far: 1.Enabled CDC and confirmed it’s working for other tables. 2.Added the new table to the publication 3.Checked that the table appears under pg_publication_tables. 4.Ran a manual sync in Airbyte, but the new table is still missing. Any ideas on what might be causing this or steps I should try next? Thanks in advance for your help!

Based on the information you've provided, it seems like you've followed the correct steps to add a new table to your CDC setup in Airbyte. However, there's one more step you might need to take in the Airbyte UI. According to a [forum post](https://discuss.airbyte.io/t/963) on the Airbyte community, when a new table is added to the source, you need to refresh the source schema in the Airbyte UI. This action will update the list of tables that Airbyte is aware of. However, please note that this action will reset all existing tables in the connection. Here's what you can do: 1. Go to the Airbyte UI. 2. Navigate to the connection settings for your Postgres to BigQuery connection. 3. Click on "Refresh schema" and then update the selection of tables you want to sync. Please note that this is a known issue and there's an open [GitHub issue](https://github.com/airbytehq/airbyte/issues/6912) for it. You can subscribe to this issue for updates. If refreshing the schema doesn't solve your problem, it might be a good idea to open a new topic on the [Airbyte forum](https://discuss.airbyte.io/) or comment on the existing GitHub issue with your specific problem.

@kapa.ai i've clicked on refresh source schema manually, but it didn't add new table

If you've manually refreshed the source schema and the new table is not being added, there could be a few reasons for this. 1. Time delay: For self-managed users, Airbyte checks for any changes in your source schema immediately before syncing, at most every 24 hours. This means your source schema changes may not be automatically propagated if it has been less than 24 hours since the previous schema check. For Cloud users, Airbyte checks for changes at a maximum of every 15 minutes per source ([source](https://docs.airbyte.com/using-airbyte/schema-change-management#detecting-schema-changes)). 2. Connector version: Ensure that you are using the latest version of the connector. If you are using Airbyte Open Source, you need to manually update the connector image in your local registry ([source](https://docs.airbyte.com/integrations/sources/asana-migrations#connector-upgrade-guide)). 3. Schema changes not detected: Not all types of schema changes are detected. For example, if a column's data type changes, the data in the destination will remain the same. You will need to refresh the schema and refresh the stream to ensure the data types are consistent ([source](https://docs.airbyte.com/using-airbyte/schema-change-management#detecting-schema-changes)). 4. Issues with the connector: There could be issues with the connector itself. For example, there have been reported issues with the MySQL connector not automatically refreshing the source schema when changes are made ([source](https://github.com/airbytehq/airbyte/issues/40235)). If you've checked all of these and the new table is still not being added, it would be best to report this issue to the Airbyte team for further investigation.