Skip to content

Corrupt breadcrumbs in captureException #9717

Closed
@dmudro

Description

@dmudro

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

I have a concerning case in our cloud @sentry/nextjs instance as I am seeing incorrect information attached in the breadcrumbs.

Our fairly standard Sentry implementation hosted in Vercel logs issues via captureException; a serverless function attaches extra data in captureException(think of custom transaction id and data) so that the extra data is available in Sentry UI via breadcrumbs.

In one particular issue instance there is completely unrelated data in breadcrumbs. The issue itself was expected but down in the breadcrumbs I see data matching another lambda execution running 5 minutes earlier (that execution did not log any issue Sentry). I literally see someone else's transaction id in the breadcrumb running 5 minutes later.

It almost looks like an issue with AWS Lambda global scope inside Sentry's Node package which would raise concerns.

Apologies for a rather abstract description though am not able to replicate (having the corrupt issue archived). Am opening this ticket to see if there is or has been a known similar issue before. Or maybe someone from the Sentry team might be able to relate to another bug or a sub-optimality in the code base. Found a GH ticket about global Sentry.setUser() but that's probably a long shot.

The app was running @sentry/nextjs v7.75.1 at the time.

Expected Result

Breadcumb trace should belong to the current execution

Actual Result

Breadcumb trace logs data from earlier Lambda execution (in memory)

Product Area

Issues

Link

No response

DSN

https://[email protected]/5680289

Version

7.75.1

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    No status

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions