-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unhandled errors are captured as handled errors (@sentry/node) #5375
Comments
Hey, thanks for writing in! Could you provide a more detailed reproduction to help us debug this? Are you using any integrations? |
Hi @AbhiPrasad, yes I'm using Sentry.Integrations.Http, Tracing.Integrations.Express and Tracing.Integrations.Postgres. I'm not really sure on what other details would help, this is my first time working with sentry. |
This is a known problem, unfortunately - our |
Ok, thanks for clarifying. |
We've improved this in the latest version of the |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which package are you using?
@sentry/node
SDK Version
7.3.1
Framework Version
7.3.1
Link to Sentry event
No response
Steps to Reproduce
Expected Result
The error is captured as unhandled (handled = false)
Actual Result
The error is captured but is marked as handled (handled = true).
What is setting the handled flag as true?
The text was updated successfully, but these errors were encountered: