Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update faq #6056

Merged
merged 6 commits into from
Sep 13, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 0 additions & 21 deletions website/docs/faqs/Troubleshooting/access_token_error.md

This file was deleted.

19 changes: 19 additions & 0 deletions website/docs/faqs/Troubleshooting/auth-expired-error.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: Receiving an `authentication has expired` error when trying to run queries in the IDE.
description: "Reauthenticate warehouse when seeing `authentication has expired` error"
sidebar_label: 'Receiving `authentication has expired` error in the IDE'
---

If you see a `authentication has expired` error when you try to run queries in the dbt CLoud IDE, this means your [OAuth](/docs/cloud/manage-access/set-up-snowflake-oauth) connection between Snowflake and dbt Cloud has expired.

To fix this, you must reconnect the two tools.

Your Snowflake administrator can [configure](/docs/cloud/manage-access/set-up-snowflake-oauth#create-a-security-integration) the refresh tokens' validity, which has a maximum 90-day validity period.

To resolve the issue, complete the following steps:

1. Go to your **Profile settings** page, accessible from the navigation menu.
2. Navigate to **Credentials** and click on the project you're experiencing the issue with.
3. Under **Development credentials**, click the **Reconnect Snowflake Account** (green) button. This steps you through reauthentication using the SSO workflow.

If you've tried these step and are still getting this error, please contact the Support team at support@getdbt.com for further assistance.
2 changes: 1 addition & 1 deletion website/docs/guides/debug-errors.md
Original file line number Diff line number Diff line change
Expand Up @@ -395,7 +395,7 @@ If you just opened a SQL file in the `target/` directory to help debug an issue,
Here are some useful FAQs to help you debug your dbt project:

- <FAQ path="Troubleshooting/generate-har-file" />
- <FAQ path="Troubleshooting/access_token_error" />
- <FAQ path="Troubleshooting/auth-expired-error" />
- <FAQ path="Troubleshooting/could-not-parse-project" />
- <FAQ path="Troubleshooting/gitignore" />
- <FAQ path="Troubleshooting/job-memory-limits" />
Expand Down
5 changes: 5 additions & 0 deletions website/vercel.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,11 @@
"cleanUrls": true,
"trailingSlash": false,
"redirects": [
{
"source": "/faqs/Troubleshooting/access_token_error",
"destination": "/faqs/Troubleshooting/auth-expired-error",
"permanent": true
},
{
"source": "/faqs/Models/unique-model-names",
"destination": "/faqs/Project/unique-resource-names",
Expand Down
Loading