<#C01AHCD885S|ask-ai> I just setup a new Airbyte c...
# ask-ai
j
#ask-ai I just setup a new Airbyte cluster and am trying to load data into an existing database that I was previously loading with a different airbyte cluster. I am unable to get the streams to run. What do I do?
k
If you have set up a new Airbyte cluster and are trying to load data into an existing database that was previously loaded by a different Airbyte cluster, but your streams are not running, there are a few important considerations and troubleshooting steps: 1. Stream Uniqueness Requirement Airbyte now requires that stream identifiers (stream name + namespace) be unique across all connections that share a destination. If you try to sync to the same destination stream from multiple connections (even from different clusters), Airbyte will prevent this to avoid data loss or collisions. You must use a unique stream prefix or a unique namespace for each connection. If you want to combine data from multiple sources into a single table, you should do so downstream of Airbyte, not within Airbyte itself. [More details here](https://docs.airbyte.com/platform/using-airbyte/configuring-schema#stream-uniqueness) and in the [release notes](https://docs.airbyte.com/release_notes/v-1.6#unique-stream-prefixes-or-namespaces-are-now-mandatory). 2. Migrating Configurations and State If you are migrating from one Airbyte deployment to another and want to preserve your connection configurations and incremental sync state (so you don’t have to re-backfill data), you need to export and import the complete configuration. Both Airbyte instances must be on the same version for this to work. This process will help you avoid issues with incremental streams not running due to missing state. [See this forum post for details](https://discuss.airbyte.io/t/370). 3. Troubleshooting Connection Issues - Check the Airbyte UI for error messages on the connection status page. Airbyte will display configuration errors (in red), system errors (in yellow), or rate-limiting issues. Follow the recommended actions, such as re-testing and saving the source/destination configuration, or waiting for rate limits to reset. - If you see errors related to stream collisions, adjust your stream prefix or namespace as described above. - If you migrated connections but did not migrate state, incremental syncs may not run as expected and may require a full re-sync or manual state update. [Connection troubleshooting guide](https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/review-connection-status#connection-troubleshooting). Summary of what to do: - Ensure your new connection uses a unique stream prefix or namespace. - If you need to preserve incremental sync state, export/import your Airbyte configuration and state from the old cluster to the new one. - Review the Airbyte UI for specific error messages and follow the troubleshooting steps provided. If you need more specific help, please provide the exact error message you are seeing in the Airbyte UI.