Error Handling

TL;DR

The issue may be resolved by checking the serialization or deserialization of the CustomApiError object, as it loses its instanceof check in the beforeSend step.

Guidance

• Review the beforeSend function in the Sentry configuration to ensure it does not modify the error object in a way that would cause it to lose its instanceof CustomApiError check.
• Verify that the CustomApiError class is properly defined and exported, and that it is being correctly instantiated and thrown in the server component.
• Check the documentation for @sentry/nextjs version 8.x to see if there are any known issues or configuration options related to error serialization or deserialization.
• Test the beforeSend function with a minimal example to isolate the issue and determine if it is specific to the CustomApiError class or a more general problem with error handling.

Example

No code example is provided as the issue is more related to configuration and error handling rather than a specific code snippet.

Notes

The issue may be specific to the @sentry/nextjs version 8.x or the Next.js version 14.2.4, and upgrading or downgrading these dependencies may resolve the issue. However, without further information, it is difficult to determine the root cause.

Recommendation

Apply a workaround by modifying the beforeSend function to properly handle the CustomApiError object, such as by using a custom serializer or deserializer. This will allow for more control over how the error object is processed and may resolve the instanceof check issue.