Fix Fixa integration URL

[souredoutlook]

Fix broken Fixa integration URL.

The URL https://fixa.dev/docs/integrations/sentry returns a 404 error. Updated to use the main Fixa site URL instead.

  

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sentry-docs	Ready	Preview	Oct 8, 2026 4:41pm UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
develop-docs	Ignored	Preview	Oct 8, 2026 4:41pm UTC

[github-actions]

Please update the IS YOUR CHANGE URGENT? section of the PR description:

• Select exactly one option.
• If you selected an urgent or other deadline, provide the date as YYYY-MM-DD.

This information helps the Docs team prioritize your review.

[cursor]

The Fixa list link now points at a different destination. The plan checks pageload failures, client errors, and Next.js render errors. An issue escalates when pageload failures appear or client errors jump.

Services: sentry-docs.

Mention @change-monitor in a comment to update the plan.

Plan

What changed

Readers of /integrations/third-party-integrations/ now follow Fixa to https://fixa.dev/about. The old URL https://fixa.dev/docs/integrations/sentry returned 404. This is live after sentry-docs deploys.

Risk

A broken MDX render can hide the whole third-party integrations list. Redirects that land on that list then miss the page. A wrong href only sends Fixa readers to the wrong external site.

Intended effect

This change is a docs href edit. Sentry does not record the outbound Fixa URL. There is no queryable signal that the new destination is live. Pageviews of the list are not proof the href changed. Treat intended effect as unknown unless a later check can read the published markup.

Regression watch

This diff can break render of the third-party integrations list. The same catch-all route serves that page and its sibling docs pages. Production transactions use /:path*?, so watches are on that route family.

Signal	Baseline	Rule	Source
Pageload internal errors	0 events in 2026-10-09T10:57:56Z to 2026-10-10T10:57:56Z	Rise above 0	Sentry org sentry project docs. Query: span.op:pageload environment:production span.status:internal_error
Client errors, hourly	1-48 events per complete hour in that 24h window. Total 328 events. Exclude the incomplete current hour.	Stay above 48 events in an hour	Sentry org sentry project docs. Query: production error count per hour
Next.js render error Error: Should not already be working.	4 events in that 24h window	Rise above 4 events in 24h	Sentry org sentry project docs. Query: environment:production title:"Error: Should not already be working."
Navigation p95 on /:path*?	2089ms in that 24h window. Count 4887 sampled spans.	Rise above 2089ms	Sentry org sentry project docs. Query: span.op:navigation environment:production transaction:"/:path*?"

If client errors rise, inspect titles on the same project. Known noise in this window includes promise-rejection and Algolia fetch failures.

Not observable

Outbound clicks to https://fixa.dev/about have no Sentry signal. HTTP status of fixa.dev is outside this ship. Traces scoped to /integrations/third-party-integrations/ are not usable. Client transactions are /:path*?. A URL filter over 7d returned 0 pageloads.

Get Slack DMs about this change: cursor.com/automations/rollouts