Nikita Ogorodnikov

Hello @MikeFot! Thanks for the details. I don't think it is somehow related to the background events, here we have a some non-successful status code returned by the Datadog intake,...

@MikeFot Thanks a lot for a quick return. This log indeed makes things a bit more clear, I have additional questions now: * Are you using proxy/custom endpoint in Datadog...

I think here the issue is that your custom endpoint is replying with status code `200`, while Datadog intake replies with status code `202` when request is accepted. In this...

Hello @MikeFot, @nicbell! I'm closing this ticket due to inactivity and I hope your problem was solved. Feel free to re-open it if needed.

Hello @ihermandev! Thanks for opening the issue. Can you please post the full stacktrace of the error happening?

Hello @ihermandev! Thanks for sharing stacktrace (I edited it and removed non-relevant threads). It seems that it is a bug in the `androidx.metrics:metrics-performance` library we are using under the hood....

I've opened a [bug in the Google Issue Tracker](https://issuetracker.google.com/issues/311218678), you can star it to see the updates.

@Aetherna this is an issue in `androidx.metrics:metrics-performance` library and was reported [here](https://issuetracker.google.com/issues/311218678?pli=1). Once fix is out we will update the library used.

There is a [new release](https://issuetracker.google.com/issues/311218678#comment13) of AndroidX Metrics library which should fix the problem, however it is written there that: > It is possible this bug has only been partially...

Hello @cmtanko! I hope that your question was answered and I'm closing this issue. Please feel free to re-open it if needed.