@sentry/nextjs not reporting issues i serverless functions

• Review the documentation: https://docs.sentry.io/
• Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
• Use the latest release: https://github.com/getsentry/sentry-javascript/releases
• Provide a link to the affected event from your Sentry account

Package + Version

• @sentry/browser
• @sentry/node
• raven-js
• raven-node (raven for node)
• other:

Version:

6.5.1

Description

I’ve recently started using the @sentry/nextjs package for a Nextjs site. I’ve followed through with the installation guide with one exception. I’m using environment variables instead of the file generated by the wizard. On the client side it works great, the releases and bugs are being tracked, but I’m getting no reports from my serveless functions when they throw errors.

import { withSentry } from "@sentry/nextjs";

const handler = async (req, res) => {
  throw new Error("API throw error test");
  res.status(200).json({ name: "John Doe" });
};

export default withSentry(handler);

This is the serverless function I am testing and nothing is showing up in my Sentry dashboard when it fails.

[AbhiPrasad]

Hey everyone, thanks for all the comments and feedback.

We are currently working on a patch to fix these issues (and some of the linked issues) by changing how we do server side initialisation of the Sentry SDK - we hope to push something out ASAP.

[DavidChouinard]

For context: we had this issue when we first manually integrated Sentry with Vercel (before the Next.js plugin). The issue, as I remember, is that Sentry queues up exceptions to be sent to the server but Vercel terminates the function instantaneously — causing the exception to be lost.

Adding await Sentry.flush(2000) to the error path fixed the issue, the Next.js library should probably do that by default.