feat: add isolate_context_by_message setting

[Litarnus]

DESCRIBE YOUR PR

Tell us what you're changing and why. If your PR resolves an issue, please link it so it closes automatically.

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

• Urgent deadline (GA date, etc.):
• Other deadline:
• None: 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 added an urgent due date to it.
  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 (UTC)
develop-docs	Ready	Preview, Comment	May 15, 2026 9:31pm
sentry-docs	Ready	Preview, Comment	May 15, 2026 9:31pm

[sentry]

Bug: The documentation for capture_soft_fails is inconsistent; the prose states the default is true, but the configuration example shows false.
_{Severity: MEDIUM}

Suggested Fix

Update the YAML configuration example block to reflect the correct default value. Change capture_soft_fails: false to capture_soft_fails: true to match the descriptive text and the actual default behavior.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: docs/platforms/php/guides/symfony/configuration/symfony-options.mdx#L119

Potential issue: The new documentation prose correctly states that `capture_soft_fails`
defaults to `true`. However, a pre-existing YAML configuration example block in the same
document shows `capture_soft_fails: false`. This contradiction is introduced by the new
text. Users who copy the example configuration will inadvertently override the true
default, disabling the capture of soft-fail exceptions for retried messages and creating
a silent gap in error visibility.

_{Did we get this right? 👍 / 👎 to inform future reviews.}