This is a bug Paul, specifically with the O365 activities and it only affects Background processes if I recall correctly.
Give me a few and I’ll see if I can find a reference where I report it to a product manager.
Ok, it seems it was something I perhaps talked to them about on a ticket and I don’t have access to that right now. But basically this occurs because of a bug in the O365 packages and has the bizarre nuance that it only affects background processes, not foreground ones (if my memory serves me correctly).