Solution skill
Sentry: errors arrive but transactions do not (or the reverse)
Complete solution
Shows how to fix sentry: errors arrive but transactions do not (or the reverse). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
For "ignoreErrors": set debug: true, trigger one error and one transaction, and watch the SDK logs: you will see the error envelope sent and either the transaction envelope sent, sampled out, or never created. No sample rate set. traces\sample\rate/tracesSampleRate unset means tracing is off entirely. Check for an env var overriding your config. Check client-side filtering before suspecting transport, since transport would break both.
ignoreErrorsWhen to use
You are seeing this: Error monitoring is always on once the SDK is initialized with a DSN. Use this skill when you run into "Sentry: errors arrive but transactions do not (or the reverse)".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
They are independent pipelines
Error monitoring is always on once the SDK is initialized with a DSN. Tracing is opt-in and needs two things: a sample rate AND a transaction source. One working without the other is normal, not a contradiction.
Errors yes, transactions no
- No sample rate set.
traces_sample_rate/tracesSampleRateunset means tracing is off entirely. This is the most common cause. - No transaction source. In Python, spans are only created inside an existing transaction; outside a supported framework you must create one with
start_transaction(orstart_spanin newer versions). A plain script with a sample rate but no transaction produces nothing. - Sample rate is 0. Zero means no new traces start. Check for an env var overriding your config.
- v11 JS: filters referencing transactions.
beforeSendTransactionandignoreTransactionsno longer do anything in stream mode. If transactions vanished after upgrading, a filter did not break; the hook simply stopped being called.
Transactions yes, errors no
This direction is rarer and usually means error events are filtered: beforeSend returning undefined, ignoreErrors matching too broadly, or inbound filters in project settings. Check client-side filtering before suspecting transport, since transport would break both.
Confirmation
Set debug: true, trigger one error and one transaction, and watch the SDK logs: you will see the error envelope sent and either the transaction envelope sent, sampled out, or never created. Sampled-out vs never-created tells you whether the rate or the source is the problem.
Verify
After the fix, both an issue and a trace for the same request should appear, linked together in the issue details. If they appear unlinked, the trace propagation headers are being stripped by a proxy between services.
Evidence
Researched against live Sentry docs 2026-09-26. The Python setup page (docs.sentry.io/platforms/python/) documents issues as always enabled and tracing as opt-in via tracessamplerate, with spans only created within an existing transaction and manual starttransaction needed outside supported frameworks. The Python options page (docs.sentry.io/platforms/python/configuration/options/) documents that either tracessamplerate or tracessampler must be defined to enable tracing. The v10-to-v11 migration guide (docs.sentry.io/platforms/javascript/migration/v10-to-v11/) documents stream mode as the v11 default and that scope tags/extra no longer reach spans.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_rXp9EIyWpf8xfGGjFbk8Ig" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Sentry: errors arrive but transactions do not (or the reverse) <span>— Vectle</span></a>