# Run fails when updating snowflake to key authentication

**URL:** <https://discourse.getdbt.com/t/run-fails-when-updating-snowflake-to-key-authentication/18572>\
**Category:** Help\
**Tags:** snowflake, dbt-cloud, dbt-core\
**Created:** [March 10, 2025, 4:59pm UTC](https://discourse.getdbt.com/t/run-fails-when-updating-snowflake-to-key-authentication/18572 "2025-03-10T16:59:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tylerbrentondavis](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/tylerbrentondavis/32/5392_2.png) [@tylerbrentondavis](https://discourse.getdbt.com/u/tylerbrentondavis)\
**Post date:** [March 10, 2025, 4:59pm UTC](https://discourse.getdbt.com/t/run-fails-when-updating-snowflake-to-key-authentication/18572/1 "2025-03-10T16:59:17Z")

</div>

I’m trying to update our instance’s credentials to a key pair authentication method from snowflake. The instance of dbt cloud runs in the IDE but on a scheduled run or a manual production run it fails and throws an incorrect username or password error.

I’ve already tried running a full refresh in the ide, the scheduled run still fails.  
I have tried creating a fresh production job and this also fails.  
I have combed through the files in the actual job to see if I’m missing a hard coded value or some other strange thing, this has been a dead end.

I can execute a successful run in the IDE with this authentication setup, but I cannot execute a successful run in my jobs.

Please advise

---

<div class="post-metadata">

**Author:** ![a\_slack\_user](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/a_slack_user/32/1629_2.png) [@a\_slack\_user](https://discourse.getdbt.com/u/a_slack_user)\
**Post date:** [March 10, 2025, 5:07pm UTC](https://discourse.getdbt.com/t/run-fails-when-updating-snowflake-to-key-authentication/18572/2 "2025-03-10T17:07:26Z")

</div>

This is my question from the help platform, please feel free to let me know if you’ve come across this error. We can’t seem to locate where the credential issue is coming from, it looks kind of like a bug

Note: `@tdavis` originally [posted this reply in Slack](https://getdbt.slack.com/archives/CBSQTAPLG/p1741626433096899?thread_ts=1741625981.760789&cid=CBSQTAPLG). It might not have transferred perfectly.

---

<div class="post-metadata">

**Author:** ![a\_slack\_user](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/a_slack_user/32/1629_2.png) [@a\_slack\_user](https://discourse.getdbt.com/u/a_slack_user)\
**Post date:** [March 11, 2025, 3:15pm UTC](https://discourse.getdbt.com/t/run-fails-when-updating-snowflake-to-key-authentication/18572/3 "2025-03-11T15:15:51Z")

</div>

we resolved this, apparently you also have to change the credentials on the job itself not just in the cloud instance.

Note: `@tdavis` originally [posted this reply in Slack](https://getdbt.slack.com/archives/CBSQTAPLG/p1741706132054169?thread_ts=1741625981.760789&cid=CBSQTAPLG). It might not have transferred perfectly.