Failed to launch the refresh schema activity because of: scheduledEventId=17, startedEventId=18, activityType='RefreshSchema', activityId='c74c8224-b48f-33e8-897b-c264db4debd8', identity='', retryState=RETRY_STATE_NON_RETRYABLE_FAILURE

Trying to upgrade to Destinations v2 for Snowflake, but running into this error on the MySQL source in the connection

Failure reason: Failed to detect if there is a schema change. If the error persist please contact the support team.

Based on the information provided in the extracts, it seems like you're encountering an issue while upgrading to Destinations V2 for Snowflake and using MySQL as a source. One possible reason for this error could be related to the permissions on the target schema in Snowflake. As mentioned in the [documentation](https://docs.airbyte.com/integrations/destinations/snowflake), if you receive an error stating

Current role does not have permissions on the target schema

, make sure that the Snowflake destination

SCHEMA

is one that the role you've provided has permissions on. Another possible reason could be related to the version of your connectors. As per the [release notes](https://docs.airbyte.com/release_notes/upgrading_to_destinations_v2), Destinations V2 is effective as of version 3.1.0+ for Snowflake and 2.0.0+ for MySQL. Please ensure that you are using these versions or later. If you're still encountering issues, it would be helpful to have the full logs and the connector versions, as suggested in the [forum post](https://discuss.airbyte.io/t/3612). If none of these solutions work, you might want to consider reaching out to the Airbyte support team or the community on their [forum](https://discuss.airbyte.io) for further assistance.

@kapa.ai the link says it might help to give more resources to temporal, how should I do that?

To allocate more resources to Temporal, you need to adjust the environment variables in the

docker.compose.yaml

file. Specifically, you should look at the

SQL_MAX_IDLE_CONNS

and

SQL_MAX_CONNS

variables.

SQL_MAX_IDLE_CONNS

controls the number of idle connections Temporal maintains. By default, this value is set to

20

. You may want to increase this number if you need more idle connections. However, be aware that Temporal creates multiple pools and the number specified might end up allowing 4-5 times more connections than expected.

SQL_MAX_CONNS

is the maximum number of connections that Temporal can have. If you increase

SQL_MAX_IDLE_CONNS

, you will also need to increase

SQL_MAX_CONNS

because

SQL_MAX_IDLE_CONNS

is capped by

SQL_MAX_CONNS

. Here's the relevant extract from the documentation: > Temporal maintains multiple idle connections. By the default value is

20

and you may want to lower or increase this number. One issue we noticed is that temporal creates multiple pools and the number specified in the

SQL_MAX_IDLE_CONNS

environment variable of the

docker.compose.yaml

file might end up allowing 4-5 times more connections than expected. If you want to increase the amount of allowed idle connexion, you will also need to increase

SQL_MAX_CONNS

as well because

SQL_MAX_IDLE_CONNS

is capped by

SQL_MAX_CONNS

. Please note that these changes should be made with caution and understanding of your workload and system resources. If you need further assistance, don't hesitate to reach out to the Airbyte community on Slack or through their support channels. Source: [Airbyte Documentation](https://docs.airbyte.com/operator-guides/scaling-airbyte)