fix(server-utils): Don't capture caller-handled LangGraph errors - #23594
Merged
nicohrubec merged 1 commit intoAug 26, 2026
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 1d2b83c. Configure here.
Contributor
size-limit report 📦
|
nicohrubec
force-pushed
the
fix/langgraph-instrumentation-error-capture
branch
from
August 26, 2026 08:52
1d2b83c to
0c6e3f9
Compare
LangGraph's compiled-graph invoke and tool-node wrappers called captureException with handled: false and then rethrew. The error rejects invoke() to the caller, so the instrumentation recorded an "unhandled crash" for an error the application handles, the same issue fixed for the client wrappers (#23024) and LangChain. The span is still marked failed and the error still propagates; only the event goes away. The integration tests masked these with .ignore('event'); those masks are removed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
nicohrubec
force-pushed
the
fix/langgraph-instrumentation-error-capture
branch
from
August 26, 2026 09:13
0c6e3f9 to
9b18d3d
Compare
nicohrubec
marked this pull request as ready for review
August 26, 2026 09:24
nicohrubec
requested review from
JPeer264,
andreiborza and
isaacs
and removed request for
a team
August 26, 2026 09:24
andreiborza
approved these changes
Aug 26, 2026
nicohrubec
added a commit
that referenced
this pull request
Aug 26, 2026
nicohrubec
added a commit
that referenced
this pull request
Aug 26, 2026
Backport of: #23594 ## Differences to the original PR - On v10 the LangGraph instrumentation lives in `packages/core/src/tracing/langgraph/` (it moved to `@sentry/server-utils` on v11), so the change is applied there with v10's internal imports. - v10's `instrumentStateGraphCompile` has an extra `catch` around `compile()` that also captured the error. That site does not exist on v11, but it is the same caller-handled pattern, so it is dropped too. v10 now has zero LangGraph captures, matching develop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

LangGraph's compiled-graph invoke wrapper and tool-node wrapper called
captureException(error, { handled: false })and then rethrew. The error rejectsinvoke()to the caller, so the instrumentation recorded an "unhandled crash" for an error the application handles. This is the same problem fixed for the OpenAI, Anthropic, and Google GenAI client wrappers in #23024, and for LangChain in #23593.Related to #23023