• It's still happening - clearly related to the 90%+ CPU on the server (not the instance, that isn't reporting CPU pressure, just the server).

    Do you have any idea what mechanism could cause a trigger failure when the CPU is busy (though not 100%)?