Hi Owain

Just a thought, but have you tried wrapping your examine stuff inside a scope? in case it's a lack of transient scope on a background thread that's causing the issue?

 using (_scopeProvider.CreateScope(autoComplete: true))
 {
         // Do your examine reading stuff here
 }

There is an answer from Shannon here that gives a bit of context:

https://our.umbraco.com/forum/using-umbraco-and-getting-started/102676-triggering-index-rebuild-via-hangfire-causes-objectdisposedexception-in-nucache#comment-321129

or might give you a steer to an answer.

regards

Marc

Hey Owain,

I think I had a similar problem when trying to do something similar with Hangfire.

For some reason, I found that some of the Umbraco services didn't work if you "just" passed the existing context. I never figured out the reason for that but instead I ended up creating my own and re-registering all the services using the following block of code:

var serviceContainer = new LightInject.ServiceContainer();
foreach (var t in (Current.Factory.Concrete as LightInject.ServiceContainer).AvailableServices)
            serviceContainer.Register(t);
serviceContainer.ScopeManagerProvider = new PerLogicalCallContextScopeManagerProvider();

See if doing the same makes a difference for you :-)

Nik

is working on a reply...