Sentry.withScope not properly clearing breadcrumbs from previous executions..

[empz]

• 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.0.2

Description

I'm following the example provided to integrate it with an Azure Function. Here's how my code looks like simplified:

const Sentry = require("@sentry/node");
Sentry.init({
  dsn: process.env["SENTRY_DSN"],
  environment: process.env["ENVIRONMENT"] || "PROD",
  sendDefaultPii: true,
});

module.exports = async function (context, myQueueItem) {
return new Promise((resolve, reject) => {
    Sentry.withScope(async (scope) => {
      try {
        // setting some context and tags
        scope.setContext("Queue Item", myQueueItem);
        scope.setTags({...});
        
        // do stuff
      }
      catch (e) {
        Sentry.captureException(e);
        await Sentry.flush(2000);

        reject(e);
      }
      finally {
        // some cleanup code...
        resolve();
      }
}

When an error is captured and sent to Sentry I can see it has breadcrumbs from previous executions instead of just the single one that throw.
Also, the context and tags are nowhere to be seen on the event.

Am I doing something wrong? If I do, could you please provide a full Azure Function example? This sample doesn't demonstrate how to properly scope context/tags to a single function invocation.

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[andreialecu]

Not sure if this will fix your issue, but try passing your scope as the second parameter:

Sentry.captureException(e, scope);

[empz]

This is really old and I'd have to go back to this to test it, but if that's the case it should be documented properly.
The docs (https://docs.sentry.io/platforms/node/guides/connect/enriching-events/scopes/#local-scopes) shows that simply calling captureException inside a withScope should take care of setting the right tags, context and breadcrumbs.

[andreialecu]

Right, but you're using an async function, so the context is probably lost.

The example you linked should probably be made more clear.

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀