Mixing express `requestHandler` with `captureException`.

[X] Review the documentation: https://docs.sentry.io/
[X] 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
[X] @sentry/node
[ ] raven-js
[ ] raven-node (raven for node)
[ ] other:

Version:

6.2.4

Description

We're using the sentry express handler in our code, which is working as expected for uncaught exceptions.

const { Sentry } = require('./sentryClient');
app.use(Sentry.Handlers.requestHandler());
// route definitions 
app.use(Sentry.Handlers.errorHandler());

However, when making one-off calls to captureException elsewhere in the codebase:

const { Sentry } = require('./sentryClient'); // same client in both cases
try {
  // some code
} catch (err) {
  Sentry.captureException(err);
}

we notice those exceptions generally have scope info from other requests attached.

Is it expected that calls to captureException outside of the middleware handler should be decorated with the same the scope info as those handled by the middleware? Should we be passing (or clearing) the scope when calling into captureException?

Can definitely provide more details, and a way to reproduce if needed, but just wanted to first check if there was something obvious we should be doing here.

getsentry / sentry-javascript