Skip to content

[Regression] Unable to get stack trace from events with multiple threads #849

@rodolfoBee

Description

@rodolfoBee

Regression of
#201
#272

Environment

Using Sentry MCP in Cursor

Steps to Reproduce

Try to use get_issue_details to get a stack trace of an issue.

Original prompt: "Can you look into this sentry error? {ISSUE-ID}"

Run the refined prompt on two issues from Sentry, one with multiple thread stack traces and one without:
Issue with threads from an android project (issue ID and organisation removed due to PII)

use the get_issue_details tool from the Sentry MCP to get the stack trace from the most recent event in this issue [redacted] from the [redacted] organisation. 

No stack trace found:

Using get_issue_details for [redacted] in the [redacted] org, the most recent event is 30f2d27f8a554b90b62e33016539f405, and its stack trace is:

No stacktrace available

Screenshot from the Sentry UI confirming the issue has stack traces:

Image

Using the same call in an issue from a Django project which has no threads and the stack trace is present in the JSON's "exception" field

use the get_issue_details tool from the Sentry MCP to get the stack trace from the most recent event in this issue DJANGO-15 from the [redacted]  organisation. 

This gives the expected result:

ValueError: The view sentryTest.urls.trigger_error didn't return an HttpResponse object. It returned None instead.
File "django/core/handlers/exception.py", line 55, in inner
    response = get_response(request)
File "django/core/handlers/base.py", line 204, in _get_response
    self.check_response(response, callback)
....

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions