-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
withServerActionInstrumentation catches NEXT_REDIRECT and NEXT_NOT_FOUND errors #10466
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
Comments
Ah right. Thanks for raising. This is an oversight but should be fixed easily. Backlogging! |
What version of sentry do you have to have to no longer have this issue? I saw you completed this in #10474, but I am still running into this. I have |
@ishaangandhi would you mind creating a new issue with a reproduction example? Thank you! |
I'm also seeing this still on newest v7 (7.116.0). Show's up in Spotlight as well during local dev. Working on a reprod but not reproducible in an isolated way yet. |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/nextjs
SDK Version
7.99.0
Framework Version
14.1.0
Link to Sentry event
https://yellowpad-tl.sentry.io/issues/4933611798/events/b027a0b732e44edfa4da10f4f6d528fa/?project=4506667113185280
SDK Setup
Steps to Reproduce
Create a server action with the following:
Expected Result
These exceptions should not be caught as per #7641.
Actual Result
An error is logged in Sentry issues:
The text was updated successfully, but these errors were encountered: