Lalleh Rafeei

A fix for this issue was released two days ago, so this fix should be available in the next release (or it can be run directly from the main branch...

Oh, it seems to be going to the right area now! I'll close the ticket.

Hello--sorry about the delay on this. I have a branch that should fix this. Could you use this branch to see if that resolves the issue for you? https://github.com/newrelic/newrelic-python-agent/tree/malformed-requests-exception You...

That's fair. In that case, I'll merge the branch and if this does not end up fixing the issue after all, we can reopen the ticket.

Hello--sorry about the delay on this. I have a branch that should hopefully fix this. If this is still an issue you are having, could you try to use this...

Hello--sorry about the delay on this one. Are you using a custom base task for any of your tasks, perhaps? We had a similar issue with this that involved New...

Hello-- Long story short, we need to do some longer term fixes to get this to work properly, but in the meantime, could you try this workaround? https://github.com/newrelic/newrelic-python-agent/issues/1243#issuecomment-2536839894

For some reason, the github ticket was closed, but the work is being tracked here: https://new-relic.atlassian.net/browse/NR-373685

Hello-- We have a branch up that should solve this issue. If anyone wants to test it out before we release it, the branch is `celery-custom-task-instrumentation`

Hi @mishikaraj --out of curiosity, how are you setting up the consumer? My concern with the proposed solution is that there is some other issue that is being masked; `destination_name`...