chore: Remove integration-specific Python queue ops

[alexander-alderman-webb]

DESCRIBE YOUR PR

Related to getsentry/sentry-conventions#693

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace YYYY-MM-DD with the due date. You can update this information later by editing the PR description.

• Urgent deadline (GA date, etc.): YYYY-MM-DD
• Other deadline: YYYY-MM-DD
• No deadline: Not urgent, can wait up to 1 week+

SLA

• Teamwork makes the dream work, so please add a reviewer to your PRs.
• Please give the docs team up to 1 week to review your PR unless you've supplied a deadline.

Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs (subject matter experts)
• PR was reviewed and approved by a member of the Sentry docs team

LEGAL BOILERPLATE

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

EXTRA RESOURCES

• Sentry Docs contributor guide

[vercel]

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

Project	Deployment	Actions	Updated
develop-docs	Ready	Preview	Oct 12, 2026 7:00am UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
sentry-docs	Ignored		Oct 12, 2026 7:00am 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 plan checks client errors, pageload failure, and navigation failure. An issue escalates when those error or failure rates rise. Telemetry cannot prove the removed table rows are gone.

Rollout complete

Services: develop-docs.

Plan

What changed

The Span Operations page no longer lists queue.task.celery, queue.task.rq, or queue.submit.celery. Readers of that page see three fewer messaging ops.

develop-docs must deploy before this change is live. The catalog id matches the develop-docs/ path, the Vercel deploy map, and the runtime project tag develop-docs.

Risk

A broken MDX table can fail render on the shared /:path* route. That route serves every developer-docs page. A build failure blocks the whole site. A runtime render error can fail this page first. Sibling pages on the same app can fail if the deploy is bad.

Intended effect

This change is a docs table edit. No counter records that those three ops left the page. Do not treat a green error rate as proof the rows are gone. intended_effect stays absent unless the executor can see the new table text by another means.

Regression watch

Traces sample at 30%. Compare like for like. Hourly rates swing on small samples. Use the 24h rate as the primary band. Existing Algolia 401 and hydration issues are noise unless they spike on the Span Operations URL.

Signal	Baseline	Window	Source	Rule
Production client error rate	4.1% (16 errors / 393 sampled pageloads). Hours with at least 10 pageloads sit at 0-12%.	2026-10-11T06:58Z to 2026-10-12T06:58Z	Sentry sentry / develop-docs, environment:production error count over span.op:pageload count	Hold the 24h rate near 4%. Escalate if it rises above 12%.
Pageload failure rate	7.6% (30 error / 393 sampled pageloads). Hours with at least 10 pageloads sit at 0-30%.	2026-10-11T06:58Z to 2026-10-12T06:58Z	Sentry sentry / develop-docs, span.op:pageload failure_rate()	Hold the 24h rate near 7-8%. Escalate if that 24h rate rises above 15%.
Navigation failure rate	0% on 433 sampled navigations. p95 duration 1.26s.	2026-10-11T06:58Z to 2026-10-12T06:58Z	Sentry sentry / develop-docs, span.op:navigation failure_rate()	Hold at 0%. Escalate if failure leaves zero.
Span Operations pageload failure	0% on 7 sampled pageloads. p95 duration 15.3s.	2026-10-05T06:58Z to 2026-10-12T06:58Z	Sentry sentry / develop-docs, span.op:pageload url.full:*span-operations*	Hold at 0%. Escalate if this URL starts to fail.

Not observable

The published table text is not in telemetry. The executor cannot confirm those three ops are gone from HTML. Sampled pageloads for that URL were 0 in the 24h window, so short-window watches on that path are empty.

[elramen]

This doesn't seem to align with conventions (task/submit vs publish/process). Is this a mistake or am I missing something?

[alexander-alderman-webb]

conventions are the source of truth.
not sure why it doesn't align.

[cursor]

Verified in production

• The live Span Operations page still omits the three queue ops, and this release had no pageload failures.