Airbyte tells me that the sync was successful, but the tables were not created at my destination

This issue can occur due to various reasons and it's not uncommon. Here are a few possible scenarios and solutions based on the knowledge sources: 1. Check the Destination Namespace Setting: In some cases, if the destination namespace is set to "Mirror source structure", the tables might not appear in the destination. Changing it to "destination default" might solve the issue ([source](https://discuss.airbyte.io/t/349)). 2. Check the Internal Tables: Sometimes, the data might be present in the internal tables. For instance, in Redshift, the data might be present in

_airbyte_raw_*

tables ([source](https://discuss.airbyte.io/t/843)). 3. Check the Connector Version: Some users have reported that downgrading the connector version solved the issue for them ([source](https://github.com/airbytehq/airbyte/issues/40670)). 4. Check for Connector Bugs: There might be bugs in the connector you're using. For instance, the Clickhouse destination connector has been reported to have issues where it only creates internal tables and not the main tables ([source](https://github.com/airbytehq/airbyte/issues/36199)). 5. Check for Long Running Operations: In some cases, operations like

DROP

and

ALTER

might take a long time to complete, leaving the tables empty for a while. This has been reported in the case of BigQuery ([source](https://github.com/airbytehq/airbyte/issues/40733)). If none of these solutions work, it would be best to report the issue on the Airbyte Github or discuss it on the Airbyte forum for more specific help.