New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Runtime instrumentation error. Request context propagation failed. No trace with id {ID}. Report this issue to New Relic support. #434
Comments
Hi @DmytroLitvinov! Thank you for reporting this. Would you be able to open this as a ticket with New Relic support? This will allow our support engineers to work directly with you to gather logging and other relevant information that will help us to debug this issue. |
Hi @umaannamalai , |
Same error here
|
Should be fixed with #441. Feel free to reopen if this issue still occurs on versions |
This just happened to me. Using
|
Related to #468? |
Tried updating starlette to 0.19.0, but no improvement. Had to go all the way back to 7.2.2.169, that version doesn't fail. |
Hi there,
After upgrading from version 7.2.2.169 to 7.2.4.171, we started to receive a lot of events (459k) in our Sentry with the next message:
We are using the next tech stack:
Command which we run to start our gunicorn:
newrelic-admin run-program gunicorn asgi -k uvicorn.workers.UvicornWorker
Seems like it was introduced after that PR
As a temporary solution, we downgrade our version to 7.2.2.169.
The text was updated successfully, but these errors were encountered: