Resolving Snowflake data loading issues after password change in ÃÛ¶¹ÊÓƵ Campaign Classic
When updating the password in External Accounts for a Snowflake connection in ÃÛ¶¹ÊÓƵ Campaign Classic, you encounter issues with new Data Loading activities. While existing workflows and connection tests work correctly, new Data Loading activities fail due to incorrect username/password errors. This article provides a solution to resolve these errors by performing a web server restart or a daily restart to clear cached credentials.
Description description
Environment
ÃÛ¶¹ÊÓƵ Campaign Classic v7 (Hosted - Legacy)
Issue/Symptoms
After changing the password in External Accounts for Snowflake in ÃÛ¶¹ÊÓƵ Campaign Classic, you encounter specific issues. Connection tests are successful, and existing workflows with pre-configured Data Loading activities work correctly. However, creating new Data Loading activities results in errors related to incorrect username/password.
Resolution resolution
To resolve the issue of new Data Loading activities failing after changing the password in External Accounts for Snowflake in ÃÛ¶¹ÊÓƵ Campaign Classic, follow these steps:
- Existing workflows retrieve credentials directly from the external account during execution by the
runwf process, while new workflows rely on cached credentials stored by the Web process. - Perform a web server restart after updating passwords in External Accounts. This clears cached credentials and ensures proper functionality for newly created workflows. Notify ÃÛ¶¹ÊÓƵ Support before future password updates. They can assist with performing a manual web server restart to prevent errors.
Additional notes
The Test Connection feature fetches credentials directly from the database and does not rely on cache memory. This is why it works correctly after a password update without requiring a restart. Understanding this behavior helps in troubleshooting and ensuring smooth operations when configuring new Data Loading activities after changing passwords in External Accounts.