I’ve experienced similar behaviour - adding and subsequently removing a “time-off” annotation was enough to trigger this: