Based on the information provided in the extracts, it’s not entirely clear what specific issue or change you’re referring to that might affect Airbyte connections with Snowflake. However, there are a few points that might be relevant: 1. In the tutorial on orchestrating ELT pipelines with Prefect, Airbyte, and dbt, it’s mentioned that you’ll need to set up three separate connections to load data for each repository into Snowflake. The sync frequency is set to manual, and only commits and issues are selected as the data to sync from GitHub to Snowflake. This is done to reduce the amount of data being synced. If these settings are not configured correctly, it could potentially affect your Airbyte connections with Snowflake. source 2. The Snowflake destination connector setup guide provides detailed instructions on setting up Snowflake entities (warehouse, database, schema, user, and role) in the Snowflake console and configuring the Snowflake destination connector using the Airbyte UI. If these steps are not followed correctly, it could affect your Airbyte connections with Snowflake. source 3. There’s a forum post where a support agent suggests updating the Airbyte version and connectors as a potential solution to issues with Airbyte connections. If your Airbyte version or connectors are outdated, it could affect your connections with Snowflake. source 4. A GitHub issue was reported where a failure to connect to Snowflake caused the destination-snowflake to go into an infinite loop. This issue was seen intermittently on a connection, and the error did not cause the sync to stop, instead, it went into an infinite loop until manually cancelled. If you’re experiencing a similar issue, it could affect your Airbyte connections with Snowflake. source Without more specific information about the issue or change you’re referring to, it’s difficult to provide a more precise answer. If you could provide more details, I might be able to give a more accurate response.