diff --git a/website/docs/faqs/Troubleshooting/access_token_error.md b/website/docs/faqs/Troubleshooting/access_token_error.md
deleted file mode 100644
index db59d3ba17a..00000000000
--- a/website/docs/faqs/Troubleshooting/access_token_error.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: I'm receiving an `access_token` error when trying to run queries in the IDE.
-description: "Reauthenticate warehouse when seeing `access_token` error"
-sidebar_label: 'Receiving `access_token` error in the IDE'
-id: access_token_error
-
----
-
-If you're seeing a database error labeled `access_token` when you try to run queries in the 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'll need to re-connect 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 gear icon at the upper right corner of dbt Cloud).
-2. Click on the correct warehouse connection under **Credentials**.
-3. Click the green **Reconnect Snowflake Account** button in the **Development Credentials** section. This drives you through reauthentication through the SSO flow. 
-
-If you've tried the step above and are still experiencing this behavior, reach out to the Support team at support@getdbt.com for further assistance.
diff --git a/website/docs/faqs/Troubleshooting/auth-expired-error.md b/website/docs/faqs/Troubleshooting/auth-expired-error.md
new file mode 100644
index 00000000000..267407a8c70
--- /dev/null
+++ b/website/docs/faqs/Troubleshooting/auth-expired-error.md
@@ -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.
diff --git a/website/docs/guides/debug-errors.md b/website/docs/guides/debug-errors.md
index 58776fa181f..442284fc6ee 100644
--- a/website/docs/guides/debug-errors.md
+++ b/website/docs/guides/debug-errors.md
@@ -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" />
diff --git a/website/vercel.json b/website/vercel.json
index f79fc959187..defdc449276 100644
--- a/website/vercel.json
+++ b/website/vercel.json
@@ -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",