Do replication tasks need to be stopped when switching Snowflake endpoint to Key Pair Authentication?

[SHARMA-G]

Hi I am in the process of updating our Snowflake endpoint in Qlik Replicate from password authentication to key pair authentication.
The connection test works fine with the new key pair setup, and tasks continue to run without interruption.

The documentation explains how to configure key pair authentication but does not explicitly state whether it is best practice to stop active replication tasks during this change, or if it is safe to apply the change while tasks are running.

Has anyone implemented this change without stopping tasks?

Did you stop tasks before updating the pw to keypair method, or continue without stopping?

Is there any risk of cached sessions or partial replication if tasks are not restarted?

Looking for clarification on recommended best practice so we can document this properly for our environment, thanks.

[Dana_Baldwin]

Hi @SHARMA-G 

Endpoint changes do not become effective until you stop and resume the tasks that use them. Endpoint settings are only read and processed during the task startup process. If you leave the tasks running after this change, they will continue to use the previous authentication that was defined on the endpoint.

Thanks,

Dana

[SHARMA-G]

So how reliable the ‘test’ is after the change to keypair while task is running. Does the test 100% confirms keypair will work and then save changes and restart task is that the correct process 

[Dana_Baldwin]

Hi @SHARMA-G 

The test connection is a basic confirmation that the configuration is correct, you can log in. It should be fine, but it cannot perform a full functionality test. You will need to restart the related tasks and test. Ideally you can perform this in a test environment before production implementation.

Thanks,

Dana

[SHARMA-G]

Thanks for confirming that the test connection only validates login and basic configuration. Could you please clarify the correct operational sequence for replication tasks in this scenario?

• If the test connection is successful, should the replication task be left running and then stopped before saving changes?
• Or is the recommended approach to save first, then restart the task to ensure the configuration is fully applied?

I’d like to be sure of the right order so that tasks are handled consistently

[Dana_Baldwin · Accepted solution]

• If the test connection is successful, should the replication task be left running and then stopped before saving changes?

No need to stop the task before saving the changes to the endpoint. You can but it is neither "right" nor "wrong". You just need to save the changes before you start the task again so they are used.

• Or is the recommended approach to save first, then restart the task to ensure the configuration is fully applied?

This is typically what users do. Make edits to the endpoint and save them, then stop and resume the tasks so they go into effect.