Hi Jay

I have had possibly similar to this happen on a V7 site before.

What was happening for me was when I called contentService.SaveAndPublishWithStatus() within my hangfire task, the cache refreshing instructions created by this action were being stored temporarily in 'HttpContext.Items' - Normally if publishing from Umbraco, the BatchedDatabaseServerMessenger handles reading these items and inserting them into the Database, but because Hangfire runs in a background thread without a context, we were faking an UmbracoContext and the instructions were being lost.

We were able to work around this by manually calling FlushBatch() on the BatchedDatabaseServerMessenger from within the Hangfire task:

contentService.SaveAndPublishWithStatus(twitterApiSettings);

                    // In a hangfire task the SaveAndPublishWithStatus isn't raising the cache refreshing events, this appears to be a way to flush the instructions into the db?
                    BatchedDatabaseServerMessenger bdsMess = ServerMessengerResolver.Current.Messenger as BatchedDatabaseServerMessenger;
                    bdsMess.FlushBatch();

Now this was V7, so I'm not sure if this will be the same in V8, or if the BatchedDatabaseServerManager exists in V8, or if the same workaround would work... :-P

(looks like it exists in V8: https://github.com/umbraco/Umbraco-CMS/blob/v8/dev/src/Umbraco.Web/BatchedDatabaseServerMessenger.cs#L26C18-L26C48 but you might need to inject the BatchedDatabaseServerMessenger in to get reference to it)

But you were asking if anyone had an idea, and this might be the sort of thing that is the cause!!

Hope it helps steer you to a solution.

regards

marc

thanks Marc I'll try it out

is working on a reply...