Hello Dojo,
I have a driver that uses an HttpClient to communicate with an API. For all of the API calls, we simply initialize the Http object, sends the request, and then disposes the object. The issue I'm having is that after we left an element with this version running the driver for a long time, it ran into an issue with accessing a disposable object after it was disposed. After we restarted the element, the issue went away and we cannot recreate it. This seems strange since the only place where this object is accessed is before we dispose it, so I'm hoping someone might know if I'm missing something. Here's one of the methods where I'm experiencing the error: 
Thank you for your help,
Bauti
Hello again,
My understanding of the issue was incorrect and had to do as the ObjectDisposedException was coming from another method called in the SendTokenizeRequest. 
While I already knew is was necessary to create a new request when we did a retry, I didn't realize that the content would be disposed of after sending the request and instead it should have been: 
This also explains why the error would not consistently show up as it was related to needing to do retries, which would happen when there was incorrect communication between DataMiner and the API.
The code looks safe as long as SendTokenizeRequest is implemented correctly, meaning it doesn’t internally rely on the HttpHelper object after returning its Task.
If SendTokenizeRequest does something like:
Task.Run(() => DoSomethingWith(httpHelper));
then the HttpHelper instance could be disposed while that background task is still using it.
If that’s not the case, are you sure the ObjectDisposedException that was thrown actually originated from the HttpHelper instance?