diff --git a/apps/docs/content/troubleshooting/edge-function-fails-deploy.mdx b/apps/docs/content/troubleshooting/edge-function-fails-deploy.mdx
index 0575a4bc0164f..38ae0f1a32b83 100644
--- a/apps/docs/content/troubleshooting/edge-function-fails-deploy.mdx
+++ b/apps/docs/content/troubleshooting/edge-function-fails-deploy.mdx
@@ -2,14 +2,15 @@
 title = "Edge Function deploy failed due to an internal error"
 topics = [ "functions" ]
 keywords = [ "fail", "deploy" ]
+database_id = "30b3f7a4-a2b7-4430-8176-31aa4d92b2e9"
 
 [[errors]]
 http_status_code = 500
-message="Function deploy failed due to an internal error"
+message = "Function deploy failed due to an internal error"
 
 [[errors]]
 http_status_code = 500
-message="unexpected deploy status 500"
+message = "unexpected deploy status 500"
 ---
 
 When encountering the `Function deploy failed due to an internal error`, try deploy the function via the [Supabase CLI](/docs/guides/local-development) with the `--debug` flag to gather extra information to identify the possible cause.
diff --git a/apps/docs/content/troubleshooting/email-template-not-updating.mdx b/apps/docs/content/troubleshooting/email-template-not-updating.mdx
index c0929a289d42a..3abba811c2d00 100644
--- a/apps/docs/content/troubleshooting/email-template-not-updating.mdx
+++ b/apps/docs/content/troubleshooting/email-template-not-updating.mdx
@@ -2,6 +2,7 @@
 title = "Email template not updating"
 topics = [ "auth", "studio" ]
 keywords = [ "email", "template" ]
+database_id = "47c4e2c7-0ff3-48e7-8c8a-912494ff8c24"
 
 [[errors]]
 code = "templatemailer_template_body_parse_error"
diff --git a/apps/docs/content/troubleshooting/how-to-delete-vercel-linked-projects-9d08aa.mdx b/apps/docs/content/troubleshooting/how-to-delete-vercel-linked-projects-9d08aa.mdx
index 3de2f2e4563c0..90e8989f2a259 100644
--- a/apps/docs/content/troubleshooting/how-to-delete-vercel-linked-projects-9d08aa.mdx
+++ b/apps/docs/content/troubleshooting/how-to-delete-vercel-linked-projects-9d08aa.mdx
@@ -2,6 +2,7 @@
 title = "How to delete Vercel linked projects"
 topics = [ "platform" ]
 keywords = [ "vercel", "delete", "marketplace", "projects", "organization" ]
+database_id = "aafe6f52-de09-44ec-b329-1bbbf26146dd"
 
 [api]
 ---
diff --git a/apps/docs/content/troubleshooting/new-branch-doesnt-copy-database.mdx b/apps/docs/content/troubleshooting/new-branch-doesnt-copy-database.mdx
index 7470a05c7c7b4..cf0beccdc7c84 100644
--- a/apps/docs/content/troubleshooting/new-branch-doesnt-copy-database.mdx
+++ b/apps/docs/content/troubleshooting/new-branch-doesnt-copy-database.mdx
@@ -2,6 +2,7 @@
 title = "Why are my Supabase branches empty?"
 topics = [ "branching" ]
 keywords = [ "branching", "migrations" ]
+database_id = "c5dae428-8dd0-4879-b312-df7f7da25986"
 ---
 
 Branching in Supabase (Branching 2.0) relies on the current migration files in your project—**not** a schema dump—when creating environments from `main`. This means if your `main` branch lacks migration history, branching will not fully capture your schema. This is a known limitation highlighted in the [Branching 2.0 documentation](/blog/branching-2-0#current-limitations). Follow the steps below to generate, synchronize, and repair your migration history for smooth branching.
diff --git a/apps/docs/content/troubleshooting/project-status-reports-unhealthy-services.mdx b/apps/docs/content/troubleshooting/project-status-reports-unhealthy-services.mdx
index 908ba689a6b3e..9fb536f57ed59 100644
--- a/apps/docs/content/troubleshooting/project-status-reports-unhealthy-services.mdx
+++ b/apps/docs/content/troubleshooting/project-status-reports-unhealthy-services.mdx
@@ -1,6 +1,7 @@
 ---
 title = "Project Status reports unhealthy services"
 topics = [ "database", "studio" ]
+database_id = "357e90d6-58a7-4347-a6c0-00622fcf9c81"
 ---
 
 ![Unhealthy services in Project Status](/docs/img/troubleshooting/project-status-unhealthy-services.png)