docs: fix symbol sets link in error tracking upload guides

contents/docs/error-tracking/_snippets/StepVerifySymbolSetsUpload.tsx

@@ -16,7 +16,7 @@ export const StepVerifySymbolSetsUpload: React.FC<StepVerifySymbolSetsUploadProp
                 className="my-2"
                 size="sm"
                 type="secondary"
-                to="https://app.posthog.com/settings/project-error-tracking#error-tracking-symbol-sets"
+                to="https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-symbol-sets"
                 external={true}
             >
                 Check symbol sets in PostHog

contents/docs/error-tracking/_snippets/suppression-rules.mdx

@@ -1,4 +1,4 @@
-Autocaptured exceptions can be ignored client-side by [configuring suppression rules](https://app.posthog.com/error_tracking?activeTab=configuration#selectedSetting=error-tracking-suppression-rules) in PostHog settings. You can only filter based on the exception type and message attributes because the stack of an exception may still be minified client-side.
+Autocaptured exceptions can be ignored client-side by [configuring suppression rules](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-suppression-rules) in PostHog settings. You can only filter based on the exception type and message attributes because the stack of an exception may still be minified client-side.
 
 <ProductScreenshot
     imageLight="https://res.cloudinary.com/dmukukwp6/image/upload/suppression_rule_light_8db44eb6b1.png"

contents/docs/error-tracking/_snippets/web-install-error-tracking.mdx

@@ -1,6 +1,6 @@
 > **Note:** A minimum SDK version of v1.207.8 is required, but we recommend keeping [up to date with the latest version](/docs/sdk-doctor) to ensure you have all of error tracking's features.
 
-You can enable exception autocapture for the JavaScript Web SDK in the **Error tracking** section of [your project settings](https://us.posthog.com/settings/project-error-tracking#exception-autocapture).
+You can enable exception autocapture for the JavaScript Web SDK on the [error tracking configuration page](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-exception-autocapture).
 
 When enabled, this automatically captures `$exception` events by default for unhandled errors and unhandled promise rejections. You can fine-tune which errors are captured by passing a configuration object to `capture_exceptions`:
 

contents/docs/error-tracking/alerts.mdx

@@ -6,7 +6,7 @@ To stay on top of issues, you can set up alerts. These enable you to post to Sla
 
 ## Issue created or reopened
 
-To alert when an issue is created or reopened, go to [error tracking's configuration page](https://app.posthog.com/error_tracking?activeTab=configuration#selectedSetting=error-tracking-alerting) and click **Alerting**. This shows you a list of existing alerts. Clicking **New notification** brings you to a page to create a new one.
+To alert when an issue is created or reopened, go to [error tracking's configuration page](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-alerting) and click **Alerting**. This shows you a list of existing alerts. Clicking **New notification** brings you to a page to create a new one.
 
 <ProductScreenshot
     imageLight="https://res.cloudinary.com/dmukukwp6/image/upload/error_alerts_create_light_1a05deef21.png"
@@ -78,6 +78,6 @@ import { CalloutBox } from 'components/Docs/CalloutBox'
 
 <CalloutBox icon="IconInfo" title="Can't find your alert?" type="fyi">
 
-  If you'd like a destination to be added that we don't yet support, [let us know in-app](https://app.posthog.com/project/2#panel=support%3Afeedback%3Aerror_tracking%3A%3Afalse).
+  If you'd like a destination to be added that we don't yet support, [let us know in-app](https://app.posthog.com/#panel=support%3Afeedback%3Aerror_tracking%3A%3Afalse).
 
 </CalloutBox>

contents/docs/error-tracking/assigning-issues.mdx

@@ -30,7 +30,7 @@ Want to assign issues to a **team** rather than an individual teammate? You can
 
 ## Automatic issue assignment
 
-You can set up automatic issue assignment through a set of rules. This can be configured in the [error tracking settings](https://app.posthog.com/error_tracking?activeTab=configuration#selectedSetting=error-tracking-auto-assignment) using **auto assignment rules**.
+You can set up automatic issue assignment through a set of rules. This can be configured in the [error tracking settings](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-auto-assignment) using **auto assignment rules**.
 
 <ProductScreenshot
   imageLight="https://res.cloudinary.com/dmukukwp6/image/upload/assignment_rules_light_1cf9a2437a.png"

contents/docs/error-tracking/capture.mdx

@@ -28,7 +28,7 @@ import { CalloutBox } from 'components/Docs/CalloutBox'
 
 ### Automatic exception capture
 
-If you followed one of our guides to [set up error tracking](/docs/error-tracking/installation) and you [enabled exception auto capture](https://app.posthog.com/project/2/error_tracking?activeTab=configuration), you'll have automatic exception capture enabled.
+If you followed one of our guides to [set up error tracking](/docs/error-tracking/installation) and you [enabled exception auto capture](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-exception-autocapture), you'll have automatic exception capture enabled.
 
 For browser SDKs (JavaScript Web, React, Next.js, etc.), you can configure which types of errors are automatically captured using the `capture_exceptions` option:
 

contents/docs/error-tracking/grouping-issues.mdx

@@ -29,7 +29,7 @@ You can group exceptions as a single issue based on their properties using custo
   classes="rounded"
 />
 
-To create a **custom grouping rule** in the [error tracking settings](https://app.posthog.com/error_tracking?activeTab=configuration#selectedSetting=error-tracking-custom-grouping):
+To create a **custom grouping rule** in the [error tracking settings](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-custom-grouping):
 
 1. Click the **Add rule** button to create a new grouping rule.
 2. Select **Any** to match any of the criteria, or **All** to match all of the criteria.

contents/docs/error-tracking/pricing.mdx

@@ -48,7 +48,7 @@ By default, we capture all unhandled errors and rejections. This can capture mor
 }
 ```
 
-Alternatively, you can disable exception autocapture completely in your [project settings](https://app.posthog.com/error_tracking?activeTab=configuration#selectedSetting=error-tracking-exception-autocapture).
+Alternatively, you can disable exception autocapture completely in your [project settings](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-exception-autocapture).
 
 ### Suppression rules
 

contents/docs/error-tracking/spikes.mdx

@@ -25,7 +25,7 @@ If an issue is too new or hasn't had enough activity to establish a meaningful b
 
 ## Configuring spike detection
 
-You can configure spike detection in the [error tracking configuration page](https://us.posthog.com/project/2/error_tracking?activeTab=configuration#selectedSetting=error-tracking-spike-detection).
+You can configure spike detection in the [error tracking configuration page](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-spike-detection).
 
 <ProductScreenshot
     imageLight="https://res.cloudinary.com/dmukukwp6/image/upload/q_auto,f_auto/pasted_image_2026_03_11_T12_43_56_983_Z_9b524d4498.png"
@@ -44,4 +44,4 @@ The following options are available:
 
 ## Getting notified about spikes
 
-You can set up alerts to be notified when a spike occurs. Head to the [alerts tab](https://app.posthog.com/error_tracking?activeTab=configuration#selectedSetting=error-tracking-spike-detection) to configure notifications to Slack, Discord, Teams, HTTP Webhook and more
+You can set up alerts to be notified when a spike occurs. Head to the [alerts tab](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-spike-detection) to configure notifications to Slack, Discord, Teams, HTTP Webhook and more

contents/docs/error-tracking/stack-traces.mdx

@@ -61,7 +61,7 @@ Compiled or minified languages requires additional information to perform a proc
 
 The `source` of a frame in the exception stack trace should point to the minified code of your application which should contain the `sourceMappingUrl` parameter denoting the location of the source map. These files must either be publicly accessible for PostHog to fetch or uploaded manually to symbolify the stack trace.
 
-You can see the symbol sets fetched by PostHog and the associated frames within the [error tracking settings](https://app.posthog.com/settings/project-error-tracking#error-tracking-symbol-sets). Any missing symbol sets will also be present along with the failure reason. From here, you can also manually upload missing symbol sets or replace existing ones.
+You can see the symbol sets fetched by PostHog and the associated frames within the [error tracking settings](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-symbol-sets). Any missing symbol sets will also be present along with the failure reason. From here, you can also manually upload missing symbol sets or replace existing ones.
 
 <ProductScreenshot
     imageLight="https://res.cloudinary.com/dmukukwp6/image/upload/Screenshot_2025_01_29_at_21_24_09_7b244773eb.png"
@@ -70,4 +70,4 @@ You can see the symbol sets fetched by PostHog and the associated frames within
     classes="rounded"
 />
 
-We strongly recommend you follow the [upload source maps](/docs/error-tracking/upload-source-maps) guide to ensure your stack traces are uploaded automatically in CI instead of manually debugging the process. If you're still having issues, [let us know in-app](https://us.posthog.com/project/2#panel=support%3Afeedback%3Aerror_tracking%3A%3Afalse).
+We strongly recommend you follow the [upload source maps](/docs/error-tracking/upload-source-maps) guide to ensure your stack traces are uploaded automatically in CI instead of manually debugging the process. If you're still having issues, [let us know in-app](https://app.posthog.com/#panel=support%3Afeedback%3Aerror_tracking%3A%3Afalse).

contents/docs/error-tracking/troubleshooting.mdx

@@ -13,7 +13,7 @@ This page covers troubleshooting for Error Tracking. For setup, see the [install
 If PostHog isn't capturing errors:
 
 1. Use the [SDK Doctor](/docs/sdk-doctor) to verify your SDKs are updated to the latest version
-2. Verify **exception capture** is enabled in the [**Configuration** tab](https://app.posthog.com/project/2/error_tracking?activeTab=configuration#selectedSetting=error-tracking-exception-autocapture) in Error Tracking
+2. Verify **exception capture** is enabled on the [**Configuration** page](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-exception-autocapture) in Error Tracking
 3. Only unhandled exceptions auto-capture. For caught errors, use `posthog.captureException()`:
 
     ```js
@@ -30,7 +30,7 @@ If PostHog isn't capturing errors:
 
 If stack traces show minified code instead of original source:
 
-1. Verify source maps are uploaded to the correct project by navigating to [Error Tracking](https://app.posthog.com/project/2/error_tracking?activeTab=configuration#selectedSetting=error-tracking-symbol-sets). You'll see warnings for missing symbol sets
+1. Verify source maps are uploaded to the correct project by navigating to [Error Tracking](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-symbol-sets). You'll see warnings for missing symbol sets
 2. Source map paths must match your production bundle URLs exactly
 3. Upload source maps *before* deploying code that references them
 

contents/docs/error-tracking/upload-source-maps/angular.mdx

@@ -88,7 +88,7 @@ You should see a comment like this in your minified JS files, for example `main-
 
 Before proceeding, confirm that source maps are successfully uploaded to PostHog. 
 
-<CallToAction className="my-2" size="sm" type="secondary" to="https://app.posthog.com/settings/project-error-tracking#error-tracking-symbol-sets" external={true}>
+<CallToAction className="my-2" size="sm" type="secondary" to="https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-symbol-sets" external={true}>
     Check symbol sets in PostHog
 </CallToAction>
 

contents/docs/error-tracking/upload-source-maps/github-actions.mdx

@@ -77,7 +77,7 @@ We recommend storing `project-id` and `api-key` in GitHub Secrets (for example,
 
 1. Confirm symbol sets are present in PostHog after the workflow runs.
 
-<OSButton variant="secondary" asLink className="my-2" size="sm" to="https://app.posthog.com/settings/project-error-tracking#error-tracking-symbol-sets" external>
+<OSButton variant="secondary" asLink className="my-2" size="sm" to="https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-symbol-sets" external>
     Check symbol sets in PostHog
 </OSButton>
 

contents/docs/error-tracking/upload-source-maps/nextjs.mdx

@@ -72,7 +72,7 @@ Before proceeding, confirm that source maps are being generated by checking for
 
 <div className="mt-4 mb-2">
 
-<OSButton variant="secondary" asLink className="mb-2" size="sm" to="https://app.posthog.com/settings/project-error-tracking#error-tracking-symbol-sets" external>
+<OSButton variant="secondary" asLink className="mb-2" size="sm" to="https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-symbol-sets" external>
     Check symbol sets in PostHog
 </OSButton>
 

contents/docs/error-tracking/upload-source-maps/nuxt.mdx

@@ -5,7 +5,6 @@ showStepsToc: true
 
 import CLIDownload from '../_snippets/cli/download.mdx'
 import CLIAuthenticate from '../_snippets/cli/authenticate.mdx'
-import StepVerifySymbolSetsUpload from '../_snippets/StepVerifySymbolSetsUpload'
 
 ## Nuxt v3.7 and above
 
@@ -73,7 +72,7 @@ Before proceeding, confirm that source maps are being properly uploaded.
 
 You can verify the injection is successful by checking your `.mjs.map` source map files for `//# chunkId=` comments. Make sure to serve these injected files in production, PostHog will check for the `//# chunkId` comments to display the correct stack traces.
 
-<OSButton variant="secondary" asLink className="my-2" size="sm" to="https://app.posthog.com/settings/project-error-tracking#error-tracking-symbol-sets" external>
+<OSButton variant="secondary" asLink className="my-2" size="sm" to="https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-symbol-sets" external>
     Check symbol sets in PostHog
 </OSButton>
 

contents/docs/error-tracking/upload-source-maps/rollup.mdx

@@ -61,7 +61,7 @@ showStepsToc: true
 
 <div className="mt-4 mb-2">
 
-<OSButton variant="secondary" asLink className="mb-2" size="sm" to="https://app.posthog.com/settings/project-error-tracking#error-tracking-symbol-sets" external>
+<OSButton variant="secondary" asLink className="mb-2" size="sm" to="https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-symbol-sets" external>
     Check symbol sets in PostHog
 </OSButton>
 

contents/docs/error-tracking/upload-source-maps/vite.mdx

@@ -64,7 +64,7 @@ Add these environment variables to your CI/CD service's project settings to auto
 
 Confirm source maps were successfully uploaded:
 
-1. Go to your [symbol sets in PostHog](https://app.posthog.com/settings/project-error-tracking#error-tracking-symbol-sets) and verify your latest upload appears.
+1. Go to your [symbol sets in PostHog](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-symbol-sets) and verify your latest upload appears.
 
 2. Check your production JavaScript files in browser dev tools. They should include a source map reference comment:
 

contents/docs/error-tracking/upload-source-maps/webpack.mdx

@@ -57,7 +57,7 @@ showStepsToc: true
 
 <div className="mt-4 mb-2">
 
-<OSButton variant="secondary" asLink className="mb-2" size="sm" to="https://app.posthog.com/settings/project-error-tracking#error-tracking-symbol-sets" external>
+<OSButton variant="secondary" asLink className="mb-2" size="sm" to="https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-symbol-sets" external>
     Check symbol sets in PostHog
 </OSButton>
 

contents/tutorials/react-error-tracking.md

@@ -72,7 +72,7 @@ Next, we'll set up PostHog to capture these errors. First, we need to install `p
 npm install posthog-js @posthog/react
 ```
 
-Next, create a `PostHogProvider.jsx` file in your `src` directory, and in it, initialize PostHog using your project token and host from [your project settings](https://app.posthog.com/settings/project). While you are there, make sure that [exception autocapture](https://app.posthog.com/settings/environment-error-tracking#error-tracking-exception-autocapture) is enabled. 
+Next, create a `PostHogProvider.jsx` file in your `src` directory, and in it, initialize PostHog using your project token and host from [your project settings](https://app.posthog.com/settings/project). While you are there, make sure that [exception autocapture](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-exception-autocapture) is enabled. 
 
 ```js
 // src/PostHogProvider.jsx