Nesting of django calls in Trace Details is incorrect

[daveisfera]

Description
Trace details are nested for django calls but they shouldn't be

Expected Behavior
The trace should be linear/non-nested so it can be viewed and used as expected

Steps to Reproduce

1. Connect newrelic to django app
2. Upload data from web requests
3. View that Trace Details are nested when they shouldn't be

Your Environment
django 3.2.16 running with python 3.9.16 on Debian Bullseye

[Ak-x]

@daveisfera Do you have any images to help us further understand this issue, or documentation you are referencing on the expectations?

[daveisfera]

Here's a screenshot. You can see the middleware calls that are "siblings" and not nested, so it's incorrectly attributing the time to the "nested functions" when they're actually running really fast and not the issue

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[daveisfera]

This is still an issue

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[workato-integration]

https://new-relic.atlassian.net/browse/NR-407829

[daveisfera]

Is there a way to view the Jira issue?