getsentry · sfanahata · Oct 29, 2025 · Oct 24, 2025 · Oct 28, 2025
diff --git a/develop-docs/sdk/telemetry/profiles/continuous-profiling-api.mdx b/develop-docs/sdk/telemetry/profiles/continuous-profiling-api.mdx
@@ -55,7 +55,7 @@ interface SentryOptions {
 The definition of a profiling session depends on the profiling type:
 
 - **Continuous Profiling**: The session starts when the Sentry SDK is configured and stops when the service terminates. `profile_session_sample_rate` controls the percentage of service instances that have profiling enabled. Sampling is re-evaluated on service restart or redeployment.
-- **UI Profiling**: The session corresponds to a user session. A user session starts with a new SDK initialization. It ends when the browser tab is closed, or alternatively, under the same conditions that end a [Replay session](/product/explore/session-replay/web/). `profile_session_sample_rate` sets the percentage of user sessions for which profiling is enabled. So this sampling decision is made once on SDK initialization.
+- **UI Profiling**: The session corresponds to a user session. A user session starts with a new SDK initialization. It ends when the browser tab is closed, or alternatively, under the same conditions that end a [Replay session](https://docs.sentry.io/product/explore/session-replay/). `profile_session_sample_rate` sets the percentage of user sessions for which profiling is enabled. So this sampling decision is made once on SDK initialization.
   - **On mobile**: Backgrounding and foregrounding the app starts a new user session, and sampling is re-evaluated. If a trace is active when the app is foregrounded, the existing profiling session continues until the last root span in that trace finishes. The new sample rate will only take effect when the profiler is next started.
 
 <Alert level="warning">

diff --git a/develop-docs/sdk/telemetry/traces/modules/ai-agents.mdx b/develop-docs/sdk/telemetry/traces/modules/ai-agents.mdx
@@ -193,5 +193,5 @@ Some attributes are common to all AI Agents spans:
 | `"xai"`             | xAI                               |
 
 ## Size Limits
-In addition to the [general size limits](/concepts/data-management/size-limits/) for events, spans, and attachments, there are specific size limits for AI integrations:
+In addition to the [general size limits](https://docs.sentry.io/concepts/data-management/size-limits/) for events, spans, and attachments, there are specific size limits for AI integrations:
 - Input messages in AI integrations recorded in the span attribute `gen_ai.request.messages` are limited to 20kB per span. Messages are trimmed and truncated if they exceed the limit, retaining the most recent messages.
diff --git a/docs/platforms/javascript/common/configuration/integrations/unhandledrejection.mdx b/docs/platforms/javascript/common/configuration/integrations/unhandledrejection.mdx
@@ -52,7 +52,7 @@ Sentry.init({
 AWS adds their own `unhandledRejection` handlers to a lambda function which results in Sentry not being able to pick these up.
 As a workaround, remove all handlers before initializing Sentry.
 
-Unfortunately, this means the AWS Lambda handler has to be <PlatformLink to="/install/cjs-layer/#alternative-initialize-the-sdk-in-code">manually wrapped</PlatformLink>.
+Unfortunately, this means the AWS Lambda handler has to be <PlatformLink to="/install/layer/#alternative-initialize-the-sdk-in-code">manually wrapped</PlatformLink>.
 
 ```JavaScript
 const Sentry = require("@sentry/aws-serverless");

diff --git a/docs/platforms/javascript/common/configuration/options.mdx b/docs/platforms/javascript/common/configuration/options.mdx
@@ -290,7 +290,7 @@ Sentry.init({
 });
 ```
 
-When set, the IPC channels used by Sentry will be prefixed with the specified namespace. Note that you need to configure the same namespace in your main process, renderer processes, and preload scripts for proper communication. See the <PlatformLink to="/platforms/javascript/guides/electron/#custom-ipc-namespace">Custom IPC Namespace section</PlatformLink> for complete setup instructions.
+When set, the IPC channels used by Sentry will be prefixed with the specified namespace. Note that you need to configure the same namespace in your main process, renderer processes, and preload scripts for proper communication. See the [Custom IPC Namespace section](/platforms/javascript/guides/electron/#custom-ipc-namespace) for complete setup instructions.
 
 </SdkOption>
 
@@ -457,11 +457,15 @@ If set to `true`, the SDK adds the [W3C `traceparent` header](https://www.w3.org
 This header is attached in addition to the `sentry-trace` and `baggage` headers.
 Set this option to `true` if your backend services are instrumented with e.g. OpenTelemetry or other W3C Trace Context compatible libraries and you want to continue traces from the client.
 
+<PlatformSection notSupported={["javascript.cordova"]}>
+
 **Important:** Make sure that your backend services' CORS configuration allows the `traceparent` header.
 Otherwise, requests might be blocked.
 Use the [`tracePropagationTargets` option](#tracepropagationtargets) to control which requests the `traceparent` header is attached to.
 See <PlatformLink to="/tracing/distributed-tracing/dealing-with-cors-issues/">Dealing with CORS Issues</PlatformLink> for more information.
 
+</PlatformSection>
+
 </SdkOption>
 
 <PlatformCategorySection supported={['browser']}>

diff --git a/docs/platforms/javascript/guides/aws-lambda/configuration/lambda-wrapper.mdx b/docs/platforms/javascript/guides/aws-lambda/configuration/lambda-wrapper.mdx
@@ -6,7 +6,7 @@ sidebar_order: 2
 
 On this page you'll learn about the options to configure the `Sentry.wrapHandler` wrapper for your Lambda function.
 
-If you're using the AWS Lambda layer with environment variables (i.e. no Sentry code in your function), skip this guide or switch to the [initializing the SDK in code](../../install/cjs-layer#alternative-initialize-the-sdk-in-code).
+If you're using the AWS Lambda layer with environment variables (i.e. no Sentry code in your function), skip this guide or switch to the [initializing the SDK in code](../../install/layer#alternative-initialize-the-sdk-in-code).
 
 ## Flush Timeout
 

diff --git a/docs/platforms/javascript/guides/aws-lambda/install/cjs-npm__v9.x.mdx b/docs/platforms/javascript/guides/aws-lambda/install/cjs-npm__v9.x.mdx
@@ -8,7 +8,7 @@ In this guide you will learn how to set up the `@sentry/aws-serverless` SDK for
 We recommend starting the SDK automatically via environment variables so that you only have to make minimal code changes to your lambda function.
 If you need more control over the SDK setup, you can also [initialize the SDK in in code](#alternative-initialize-the-sdk-in-code).
 
-However, you need to modify your code and deploy the Sentry dependencies alongside your function code. If you're looking for the most simple way to set up Sentry, you might want to use the [Lambda Layer](../cjs-layer) instead.
+However, you need to modify your code and deploy the Sentry dependencies alongside your function code. If you're looking for the most simple way to set up Sentry, you might want to use the [Lambda Layer](./layer__v9.x) instead.
 
 ## 1. Prerequisites
 

diff --git a/docs/platforms/javascript/guides/aws-lambda/install/index__v9.x.mdx b/docs/platforms/javascript/guides/aws-lambda/install/index__v9.x.mdx
@@ -18,7 +18,7 @@ Note that TypeScript can also be configured to output ESM, in which case you sho
 
 ### My Lambda function uses `require`
 
-If you are using `require()` in your function, follow the CommonJS instructions. Choose between [using our Lambda Layer (recommended)](./install/layer__v9.x) or [installing the Sentry AWS NPM package](./install/cjs-npm__v9.x).
+If you are using `require()` in your function, follow the CommonJS instructions. Choose between [using our Lambda Layer (recommended)](./install/layer__v9.x) or [installing the Sentry AWS NPM package](./install/npm__v9.x).
 
 ### My Lambda function uses `import`
 

diff --git a/docs/platforms/javascript/guides/aws-lambda/install/layer__v8.x.mdx b/docs/platforms/javascript/guides/aws-lambda/install/layer__v8.x.mdx
@@ -5,13 +5,13 @@ sidebar_order: 1
 noindex: true
 ---
 
-The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](https://docs.aws.amazon.com/Lambda/latest/dg/configuration-layers.html) instead of adding `@sentry/aws-serverless` with `npm` or `yarn` [manually](../cjs-npm).
+The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](https://docs.aws.amazon.com/Lambda/latest/dg/configuration-layers.html) instead of adding `@sentry/aws-serverless` with `npm` or `yarn` [manually](../install/npm).
 If you follow this guide, you don't have to worry about deploying Sentry dependencies alongside your function code.
 To actually start the SDK, you can decide between setting up the SDK using environment variables or in your Lambda function code. We recommend using environment variables as it's the easiest way to get started. [Initializing the SDK in code](#alternative-initialize-the-sdk-in-code) instead of setting environment variables gives you more control over the SDK setup if you need it.
 
 <Alert>
 
-This installation method **does not** work with Lambda functions running in EcmaScript Modules (ESM) mode, using `import` syntax. If you're running your function in ESM, follow the [ESM guide](../esm-npm).
+This installation method **does not** work with Lambda functions running in EcmaScript Modules (ESM) mode, using `import` syntax. If you're running your function in ESM, follow the [ESM guide](../install/npm).
 
 </Alert>
 

diff --git a/docs/platforms/javascript/guides/aws-lambda/install/layer__v9.x.mdx b/docs/platforms/javascript/guides/aws-lambda/install/layer__v9.x.mdx
@@ -4,13 +4,13 @@ description: "Learn how to add the Sentry Node Lambda Layer to use Sentry in you
 sidebar_order: 1
 ---
 
-The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](https://docs.aws.amazon.com/lambda/latest/dg/adding-layers.html) instead of adding `@sentry/aws-serverless` with `npm` or `yarn` [manually](../cjs-npm).
+The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](https://docs.aws.amazon.com/lambda/latest/dg/adding-layers.html) instead of adding `@sentry/aws-serverless` with `npm` or `yarn` [manually](./npm__v9.x).
 If you follow this guide, you don't have to worry about deploying Sentry dependencies alongside your function code.
 To actually start the SDK, you can decide between setting up the SDK using environment variables or in your Lambda function code. We recommend using environment variables as it's the easiest way to get started. [Initializing the SDK in code](#alternative-initialize-the-sdk-in-code) instead of setting environment variables gives you more control over the SDK setup if you need it.
 
 <Alert>
 
-This installation method **does not** work with Lambda functions running in EcmaScript Modules (ESM) mode, using `import` syntax. If you're running your function in ESM, follow the [ESM guide](../esm-npm).
+This installation method **does not** work with Lambda functions running in EcmaScript Modules (ESM) mode, using `import` syntax. If you're running your function in ESM, follow the [ESM guide](../npm__v9.x).
 
 </Alert>
 

diff --git a/docs/security-legal-pii/security/data-retention-periods.mdx b/docs/security-legal-pii/security/data-retention-periods.mdx
@@ -21,8 +21,8 @@ By default, new account trials are granted Team plan retention. If you are trial
 | [User Feedback](/product/user-feedback/) | 30 days | 90 days | 90 days |
 | [Profiles](/product/explore/profiling/) | 30 days | 90 days | 90 days |
 | [Crons](/product/crons/) | 30 days | 30 days | 30 days |
-| [Uptime](/product/monitoring/) | 30 days | 90 days | 90 days |
-| [Attachments](/product/issues/issue-details/attachments/) | 30 days | 90 days | 90 days |
+| [Uptime](/product/uptime-monitoring/) | 30 days | 90 days | 90 days |
+| [Attachments](/product/issues/issue-details/#attachments) | 30 days | 90 days | 90 days |
 
 <Alert>
 Starting November 2025, Team and Business plans will move from the current 90 day retention period for spans, transactions, and profiles to 30 days. **Exception:** If you are on a [Team or Business plan](https://sentry.io/settings/billing/overview/) that uses transaction-based billing, transaction retention will stay at 90 days, and sampled retention of spans data will not apply.

diff --git a/platform-includes/sourcemaps/overview/javascript.nextjs.mdx b/platform-includes/sourcemaps/overview/javascript.nextjs.mdx
@@ -32,7 +32,7 @@ module.exports = withSentryConfig(
 
 #### 2. [Optional] Customize Source Map Options
 
-Configure source map behavior using the [source maps options](/platforms/javascript/guides/nextjs/configuration/build/#source-maps-options) in your Next.js config:
+Configure source map behavior in your Next.js config:
 
 ```javascript {11-16} {filename:next.config.js}
 const { withSentryConfig } = require("@sentry/nextjs");

diff --git a/platform-includes/sourcemaps/overview/javascript.nuxt.mdx b/platform-includes/sourcemaps/overview/javascript.nuxt.mdx
@@ -53,7 +53,7 @@ When you open your browser's developer tools, the browser tries to fetch source
 
 #### 3. Source Map Options
 
-Configure source map behavior using the [source maps options](/platforms/javascript/guides/nuxt/configuration/build/#source-maps-options) in your Nuxt config:
+Configure source map behavior in your Nuxt config:
 
 ```javascript {filename:nuxt.config.ts}
 export default defineNuxtConfig({

diff --git a/platform-includes/sourcemaps/overview/javascript.solidstart.mdx b/platform-includes/sourcemaps/overview/javascript.solidstart.mdx
@@ -41,7 +41,7 @@ export default defineConfig(
 
 #### 2. Source Map Options
 
-Configure source map behavior using the [source maps options](/platforms/javascript/guides/solidstart/configuration/build/#source-maps-options) in your SolidStart config:
+Configure source map behavior in your SolidStart config:
 
 ```javascript {filename:app.config.ts}
 export default defineConfig(

diff --git a/platform-includes/sourcemaps/overview/javascript.sveltekit.mdx b/platform-includes/sourcemaps/overview/javascript.sveltekit.mdx
@@ -52,7 +52,7 @@ export default defineConfig({
 
 #### 2. Source Map Options
 
-Configure source map behavior using the [source maps options](/platforms/javascript/guides/sveltekit/configuration/build/#source-maps-options) in your Vite config:
+Configure source map behavior in your Vite config:
 
 ```javascript {filename:vite.config.js}
 import { sveltekit } from "@sveltejs/kit/vite";

diff --git a/platform-includes/sourcemaps/primer/javascript.cloudflare.mdx b/platform-includes/sourcemaps/primer/javascript.cloudflare.mdx
@@ -24,4 +24,4 @@ If you are using plain Cloudflare Workers, set `upload_source_maps = true` in yo
 upload_source_maps = true
 ```
 
-For more detailed configuration options, see the [Cloudflare Workers guide](/platforms/javascript/sourcemaps/uploading/wrangler/).
+For more detailed configuration options, see the <PlatformLink to="/sourcemaps/uploading/wrangler/">Cloudflare Workers guide</PlatformLink>.
diff --git a/platform-includes/sourcemaps/primer/javascript.nextjs.mdx b/platform-includes/sourcemaps/primer/javascript.nextjs.mdx
@@ -2,7 +2,7 @@
 
 The easiest way to configure uploading source maps is by using the [Sentry Wizard](/platforms/javascript/guides/nextjs/#step-1-install).
 
-The `@sentry/nextjs` SDK uses the Sentry webpack plugin under the hood to upload source maps. See the [Build Options](../configuration/build/#source-maps-options) page and the Sentry [webpack plugin documentation](https://www.npmjs.com/package/@sentry/webpack-plugin) for more details. If you are using Vercel, then you can also use the [Vercel integration](/organization/integrations/deployment/vercel/) to upload source maps during deployments automatically.
+The `@sentry/nextjs` SDK uses the Sentry webpack plugin under the hood to upload source maps. See the Sentry [webpack plugin documentation](https://www.npmjs.com/package/@sentry/webpack-plugin) for more details. If you are using Vercel, then you can also use the [Vercel integration](/organization/integrations/deployment/vercel/) to upload source maps during deployments automatically.
 
 **Note:** Source maps are only generated and uploaded during **production builds** (`next build`). Development builds (`next dev`) do not generate source maps for upload.
 

diff --git a/platform-includes/sourcemaps/primer/javascript.solidstart.mdx b/platform-includes/sourcemaps/primer/javascript.solidstart.mdx
@@ -6,7 +6,7 @@ The easiest way to configure uploading source maps is by using the [Sentry Wizar
 npx @sentry/wizard@latest -i solidstart
 ```
 
-The SolidStart SDK uses the Sentry Vite Plugin under the hood to upload source maps. See the [Manual Configuration](../overview/javascript.solidstart.mdx) page and the Sentry [Vite plugin documentation](https://www.npmjs.com/package/@sentry/vite-plugin/#configuration) for more details.
+The SolidStart SDK uses the Sentry Vite Plugin under the hood to upload source maps. See the [Vite plugin documentation](https://www.npmjs.com/package/@sentry/vite-plugin/#configuration) for more details.
 
 **Note:** Source maps are only generated and uploaded during **production builds** (`npm run build`). Development builds (`npm run dev`) do not generate source maps for upload.