There's a chance in 60 (very exactly!) that you will get this bug: in fact it is triggered when the timestamp of the last update falls exactly at a whole minute (for instance 12:30:00).