Fix docs build warnings (#4353)

bechols · lennessyy · web-flow · commit 38256508b340 · 2026-03-27T00:57:37.000Z
* Fix docs build warnings

* throw error on broken anchor

---------

Co-authored-by: Lenny Chen &lt;lenny.chen@temporal.io&gt;
diff --git a/docs/cloud/high-availability/failovers.mdx b/docs/cloud/high-availability/failovers.mdx
@@ -381,7 +381,7 @@ Failover testing (also known as "<ToolTipTerm term="trigger testing" />)" can:
   Manual testing confirms the failover mechanism works as expected, so your system handles incidents effectively.
 
 - **Assess replication lag**:
-  In multi-region deployment, monitoring [replication lag](/cloud/high-availability/monitoring#replication-lag-metric) between regions is crucial.
+  In multi-region deployment, monitoring [replication lag](/cloud/metrics/openmetrics/metrics-reference#temporal_cloud_v1_replication_lag_p99) between regions is crucial.
   Check the lag before initiating a failover to avoid rolling back Workflow progress.
   This is less important when using isolation domains as failover is usually instantaneous.
   Manual testing helps you practice this critical step and understand its impact.
diff --git a/docs/cloud/metrics/general-setup.mdx b/docs/cloud/metrics/general-setup.mdx
@@ -53,7 +53,7 @@ To assign a certificate and generate your metrics endpoint, follow these steps:
 
 After the page refreshes, the new metrics endpoint appears below **Endpoint**, in the form `https://<account-id>.tmprl.cloud/prometheus`.
 Use the endpoint to configure your observability tool.
-For example, if you use Grafana, see [Grafana data sources configuration](/cloud/metrics/prometheus-grafana#grafana-data-sources-configuration).
+For example, if you use Grafana, see [Grafana data source configuration](/cloud/metrics/prometheus-grafana#grafana-data-source-configuration).
 
 You can also query via the [Prometheus HTTP API](https://prometheus.io/docs/prometheus/latest/querying/api/) at URLs like:
 
diff --git a/docs/cloud/metrics/openmetrics/migration-guide.mdx b/docs/cloud/metrics/openmetrics/migration-guide.mdx
@@ -294,14 +294,14 @@ To size workloads for Temporal Cloud (for example, when migrating from self-host
 
 | Old Metric (v0)                                                                                                          | New Metric (v1)                                                                                                     | New Labels |
 | ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------- | ---------- |
-| `temporal_cloud_v0_service_latency_bucket temporal_cloud_v0_service_latency_count temporal_cloud_v0_service_latency_sum` | `temporal_cloud_v1_service_latency_p99 temporal_cloud_v1_service_latency_p95 temporal_cloud_v1_service_latency_p50` | `region`   |
+| `temporal_cloud_v0_service_latency_bucket temporal_cloud_v0_service_latency_count temporal_cloud_v0_service_latency_sum` | `temporal_cloud_v1_service_latency_p99 temporal_cloud_v1_service_latency_p95 temporal_cloud_v1_service_latency_p50` | `region`   |
 | `temporal_cloud_v0_replication_lag_bucket temporal_cloud_v0_replication_lag_count temporal_cloud_v0_replication_lag_sum` | `temporal_cloud_v1_replication_lag_p99 temporal_cloud_v1_replication_lag_p95 temporal_cloud_v1_replication_lag_p50` | `region`   |
 
 #### Schedule Metrics
 
 | Old Metric (v0)                                          | New Metric (v1)                                          | New Labels |
 | -------------------------------------------------------- | -------------------------------------------------------- | ---------- |
-| `temporal_cloud_v0_schedule_action_success_count`        | `temporal_cloud_v1_schedule_action_success_count`        | `region`   |
+| `temporal_cloud_v0_schedule_action_success_count`        | `temporal_cloud_v1_schedule_action_success_count`        | `region`   |
 | `temporal_cloud_v0_schedule_buffer_overruns_count`       | `temporal_cloud_v1_schedule_buffer_overruns_count`       | `region`   |
 | `temporal_cloud_v0_schedule_missed_catchup_window_count` | `temporal_cloud_v1_schedule_missed_catchup_window_count` | `region`   |
 | `temporal_cloud_v0_schedule_rate_limited_count`          | `temporal_cloud_v1_schedule_rate_limited_count`          | `region`   |
diff --git a/docs/cloud/metrics/reference.mdx b/docs/cloud/metrics/reference.mdx
@@ -106,17 +106,17 @@ Labels: temporal_account, temporal_namespace, operation, task_type, temporal_ser
 
 #### temporal_cloud_v0_replication_lag_bucket
 
-A histogram of [replication lag](/cloud/high-availability/monitoring#replication-lag-metric) during a specific time interval for a Namespace with high availability.
+A histogram of [replication lag](/cloud/metrics/openmetrics/metrics-reference#temporal_cloud_v1_replication_lag_p99) during a specific time interval for a Namespace with high availability.
 Labels: temporal_account, temporal_namespace, le
 
 #### temporal_cloud_v0_replication_lag_count
 
-The [replication lag](/cloud/high-availability/monitoring#replication-lag-metric) count during a specific time interval for a Namespace with high availability.
+The [replication lag](/cloud/metrics/openmetrics/metrics-reference#temporal_cloud_v1_replication_lag_p99) count during a specific time interval for a Namespace with high availability.
 Labels: temporal_account, temporal_namespace
 
 #### temporal_cloud_v0_replication_lag_sum
 
-The sum of [replication lag](/cloud/high-availability/monitoring#replication-lag-metric) during a specific time interval for a Namespace with high availability.
+The sum of [replication lag](/cloud/metrics/openmetrics/metrics-reference#temporal_cloud_v1_replication_lag_p99) during a specific time interval for a Namespace with high availability.
 Labels: temporal_account, temporal_namespace
 
 ### Schedule metrics {#schedule}
diff --git a/docs/cloud/rto-rpo.mdx b/docs/cloud/rto-rpo.mdx
@@ -75,7 +75,7 @@ Temporal has put extensive work into tools and processes that minimize the recov
 
 However, user actions on a Namespace can affect the recovery point. For example, suddenly spiking into much higher throughput than a Namespace has seen before could create a period of replication lag where the replica falls behind the active. 
 
-Temporal provides a [replication lag](/cloud/high-availability/monitoring#replication-lag-metric) metric for each Namespace. This metric approximates the recovery point the Namespace would achieve in a worst case failure at that given moment.
+Temporal provides a [replication lag](/cloud/metrics/openmetrics/metrics-reference#temporal_cloud_v1_replication_lag_p99) metric for each Namespace. This metric approximates the recovery point the Namespace would achieve in a worst case failure at that given moment.
 
 :::note
 
diff --git a/docs/develop/dotnet/standalone-activities.mdx b/docs/develop/dotnet/standalone-activities.mdx
@@ -135,7 +135,7 @@ public record ComposeGreetingInput(string Greeting, string Name);
 Running a Worker for Standalone Activities is the same as running a Worker for Workflow Activities —
 you create a Worker, register the Activity, and run the Worker. The Worker doesn't need to know
 whether the Activity will be invoked from a Workflow or as a Standalone Activity. See [How to develop
-a Worker](/develop/dotnet/core-application#run-a-dev-worker) for more details on Worker setup and
+a Worker](/develop/dotnet/core-application#run-worker-process) for more details on Worker setup and
 configuration options.
 
 [src/StandaloneActivity/Program.cs](https://github.com/temporalio/samples-dotnet/blob/main/src/StandaloneActivity/Program.cs)
diff --git a/docs/encyclopedia/context-propagation.mdx b/docs/encyclopedia/context-propagation.mdx
@@ -29,4 +29,4 @@ Each SDK provides a **context propagator** interface you implement to control wh
 
 Here are SDK-specific guides:
 
-- [Go](/develop/go/observability#context-propagation)
+- [Go](/develop/go/context-propagation)
diff --git a/docs/encyclopedia/temporal-service/temporal-service-configuration.mdx b/docs/encyclopedia/temporal-service/temporal-service-configuration.mdx
@@ -144,7 +144,7 @@ Temporal Cloud emits metrics through a Prometheus HTTP API endpoint, which can b
 For details on Cloud metrics and setup, see the following:
 
 - [Temporal Cloud metrics reference](/cloud/metrics/)
-- [Set up Grafana with Temporal Cloud observability to view metrics](/cloud/metrics/prometheus-grafana#grafana-data-sources-configuration)
+- [Set up Grafana with Temporal Cloud observability to view metrics](/cloud/metrics/prometheus-grafana#grafana-data-source-configuration)
 
 On the self-hosted Temporal Service, expose Prometheus endpoints in your Temporal Service configuration and configure Prometheus to scrape metrics from the endpoints.
 You can then set up your observability platform (such as Grafana) to use Prometheus as a data source.
diff --git a/docs/encyclopedia/visibility/search-attributes.mdx b/docs/encyclopedia/visibility/search-attributes.mdx
@@ -33,7 +33,7 @@ This information is available in the Visibility store.
 :::caution Do not use sensitive data or PII in Search Attributes
 
 Do not include sensitive data, secrets, or personally identifiable information (PII) in Search Attribute **names or values**.
-Search Attribute values are stored unencrypted in the Visibility store and are not processed by a custom [Payload Codec](/dataconversion#payload-codec).
+Search Attribute values are stored unencrypted in the Visibility store and are not processed by a custom [Payload Codec](/payload-codec#payload-codec).
 The Temporal Server must be able to read these values in plain text to support filtering and ordering, so encryption is not possible without breaking search functionality.
 
 Attribute names are also visible in Namespace configuration, query expressions, and Temporal UI.
diff --git a/docs/encyclopedia/workers/tasks.mdx b/docs/encyclopedia/workers/tasks.mdx
@@ -20,9 +20,9 @@ This page discusses the following:
 - [Workflow Task](#workflow-task)
   - [When are Workflow Tasks scheduled?](#when-workflow-tasks-scheduled)
   - [How does a Worker process a Workflow Task?](#how-worker-processes-workflow-task)
-  - [How does the SDK know which code to run?](#how-sdk-knows-code)
-  - [Workflow Tasks and Determinism](#workflow-tasks-determinism)
-  - [Performance characteristics](#workflow-task-performance)
+  - [How does the SDK know which code to run?](#how-worker-processes-workflow-task)
+  - [Workflow Tasks and Determinism](#workflow-task-failures-vs-execution-failures)
+  - [Performance characteristics](#workflow-task-execution)
 - [Workflow Task Execution](#workflow-task-execution)
 - [Workflow Task Failures vs Workflow Execution Failures](#workflow-task-failures-vs-execution-failures)
 - [Activity Task](#activity-task)
diff --git a/docs/encyclopedia/workflow/workflow-execution/workflowid-runid.mdx b/docs/encyclopedia/workflow/workflow-execution/workflowid-runid.mdx
@@ -77,7 +77,7 @@ A Workflow Id is meant to be a business-process identifier, such as customer ide
 :::caution Do not use sensitive data or PII in Workflow Ids
 
 Do not include sensitive data, secrets, or personally identifiable information (PII) as a Workflow Id.
-Workflow Ids are stored in plain text, are **not** processed by a custom [Payload Codec](/dataconversion#payload-codec), and are visible in the Temporal Web UI, CLI output, Event History, and system logs.
+Workflow Ids are stored in plain text, are **not** processed by a custom [Payload Codec](/payload-codec#payload-codec), and are visible in the Temporal Web UI, CLI output, Event History, and system logs.
 The same applies to other user-defined identifiers such as Workflow Type names, Task Queue names, Activity names, and Signal/Query/Update names.
 
 Using sensitive data in these identifiers risks exposure to anyone with Namespace access and may violate data protection regulations such as GDPR, HIPAA, or SOC 2.
diff --git a/docs/evaluate/temporal-cloud/actions.mdx b/docs/evaluate/temporal-cloud/actions.mdx
@@ -145,7 +145,7 @@ event histories. Some billable concepts are not included in these calculations s
 - Export
 - Schedule
 - Replicated Actions that occur in a
-  [Namespace replication](../../cloud/high-availability/index.mdx#high-availability-features-high-availability-features)
+  [Namespace replication](../../cloud/high-availability/index.mdx#high-availability-features)
 
 Additionally, Workflows with the `TemporalNamespaceDivision` Search Attribute set may not have accurate Billable Action
 Estimates. The estimated Billable Actions should only be treated as an estimate. If billable events exist outside of
diff --git a/docs/glossary.md b/docs/glossary.md
@@ -507,7 +507,7 @@ endpoints.
 
 <!-- _Tags: [term](/tags/term), [queries](/tags/queries), [explanation](/tags/explanation)_ -->
 
-#### [Replication Lag](/cloud/high-availability/monitoring#replication-lag-metric)
+#### [Replication Lag](/cloud/metrics/openmetrics/metrics-reference#temporal_cloud_v1_replication_lag_p99)
 
 The transmission delay of Workflow updates and history events from the active region to the standby region.
 
diff --git a/docs/production-deployment/self-hosted-guide/visibility.mdx b/docs/production-deployment/self-hosted-guide/visibility.mdx
@@ -873,12 +873,12 @@ With Temporal Cloud, you can create and rename custom Search Attributes. If you
 To manage custom Search Attributes on a self-hosted Temporal Service, use the [Temporal CLI](/cli/operator#search-attribute).
 With a self-hosted Temporal Service, you can create and remove custom Search Attributes.
 
-If you're self-hosting, verify whether your [Visibility database](/self-hosted-guide/visibility#current-and-legacy-visibility-support) version supports custom Search Attributes before proceeding. 
+If you're self-hosting, verify whether your [Visibility database](/self-hosted-guide/visibility#supported-databases) version supports custom Search Attributes before proceeding.
 
 :::caution Do not use sensitive data or PII in Search Attributes
 
 Do not include sensitive data, secrets, or personally identifiable information (PII) in Search Attribute **names or values**.
-Search Attribute values are stored unencrypted in the Visibility store and are not processed by a custom [Payload Codec](/dataconversion#payload-codec).
+Search Attribute values are stored unencrypted in the Visibility store and are not processed by a custom [Payload Codec](/payload-codec#payload-codec).
 The Temporal Server must be able to read these values in plain text to support filtering and ordering, so encryption is not possible without breaking search functionality.
 
 Attribute names are also visible in Namespace configuration, query expressions, and Temporal UI.
diff --git a/docs/production-deployment/worker-deployments/worker-versioning.mdx b/docs/production-deployment/worker-deployments/worker-versioning.mdx
@@ -310,7 +310,7 @@ Unspecified.
 :::
 
 You also want to make sure you understand how your Activities are going to work across different Worker Deployment
-Versions. Refer to the [Worker Versioning Activity behavior docs](/worker-versioning#actvity-behavior-across-versions)
+Versions. Refer to the [Worker Versioning Activity behavior docs](#choosing-behavior)
 for more details.
 
 ## Rolling out changes with the CLI
diff --git a/docs/references/configuration.mdx b/docs/references/configuration.mdx
@@ -487,7 +487,7 @@ Sets default Archival configuration for each Namespace using `namespaceDefaults`
 - `state`: Default state of the Archival for the Namespace. Supported values are `enabled` or `disabled`.
 - `URI`: Default URI for the Namespace.
 
-For more details on setting Namespace defaults on Archival, see [Namespace creation in Archival setup](/self-hosted-guide/archival#namespace-creation)
+For more details on setting Namespace defaults on Archival, see [Create an Archiving Namespace in Archival setup](/self-hosted-guide/archival#create-an-archiving-namespace)
 
 Example:
 
diff --git a/docusaurus.config.js b/docusaurus.config.js
@@ -10,7 +10,7 @@ module.exports = async function createConfigAsync() {
     url: 'https://docs.temporal.io',
     baseUrl: '/',
     onBrokenLinks: 'throw',
-    onBrokenAnchors: 'warn',
+    onBrokenAnchors: 'throw',
     favicon: 'img/favicon.ico',
     organizationName: 'temporalio', // Usually your GitHub org/user name.
     projectName: 'temporal-documentation', // Usually your repo name.
@@ -384,6 +384,9 @@ module.exports = async function createConfigAsync() {
           generateLLMsTxt: true,
           generateLLMsFullTxt: true,
 
+          // Exclude imported markdown partials that should not be published as standalone LLM docs.
+          ignoreFiles: ['docs/cloud/references/regions/private-service.md', 'docs/cloud/references/regions/gcpregions.md'],
+
           // Clean up content for better LLM consumption
           excludeImports: true,
           removeDuplicateHeadings: true,
@@ -412,13 +415,13 @@ module.exports = async function createConfigAsync() {
           customLLMFiles: [
             {
               filename: 'llms-quickstart.txt',
-              includePatterns: ['quickstarts/**', 'develop/**/set-up-*'],
+              includePatterns: ['docs/evaluate/**/*.mdx', 'docs/develop/**/*.mdx'],
               fullContent: true,
               title: 'Temporal Quickstart Guide',
             },
             {
               filename: 'llms-api-reference.txt',
-              includePatterns: ['references/**', 'cli/**'],
+              includePatterns: ['docs/references/**/*.mdx', 'docs/cli/**/*.mdx'],
               fullContent: true,
               title: 'Temporal API and CLI Reference',
             },
diff --git a/package.json b/package.json
@@ -33,7 +33,7 @@
     "e2e": "playwright test"
   },
   "resolutions": {
-    "caniuse-lite": "1.0.30001731",
+    "caniuse-lite": "1.0.30001781",
     "qs": "6.14.1"
   },
   "browserslist": {
diff --git a/yarn.lock b/yarn.lock

Original file line number	Diff line number	Diff line change
`@@ -29,4 +29,4 @@ Each SDK provides a context propagator interface you implement to control wh`
`29`	`29`
`30`	`30`	`Here are SDK-specific guides:`
`31`	`31`
`32`		`-- [Go](/develop/go/observability#context-propagation)`
	`32`	`+- [Go](/develop/go/context-propagation)`