Based on the information you've provided, it seems like you've followed the correct steps to add a new table to your Postgres source in Airbyte. However, there are a few things you could check: 1. Airbyte Catalog: Make sure your Airbyte catalog is set up correctly. If there's a discrepancy between the publication and Airbyte catalog, transaction records from the missing table would not be synced. Double-check that your catalog is in sync with the publication configuration [^1^]. 2. Replication Slot: Airbyte requires a replication slot configured only for its use. Ensure that the replication slot you're using is the one you've set up for Airbyte [^5^]. 3. Sync Frequency: If your Postgres DB is purging WAL in between Airbyte jobs, this could cause issues. Try running Airbyte sync jobs more often and extend the auto-cancellation timeout [^4^]. 4. Refresh Source Schema: If a new table gets added in the source, you might need to refresh the source schema in Airbyte. However, please note that this might reset all existing tables [^6^]. If none of these steps resolve your issue, it might be a good idea to report this as a bug to the Airbyte team. There's a similar issue reported on their GitHub page [^2^]. [^1^]: (https://discuss.airbyte.io/t/2675) [^2^]: (https://discuss.airbyte.io/t/963) [^4^]: (https://discuss.airbyte.io/t/2675) [^5^]: (https://docs.airbyte.com/integrations/sources/postgres#step-4-create-a-replication-slot-on-your-postgres-database) [^6^]: (https://discuss.airbyte.io/t/963)