I noticed a possible issue when scheduling a protocol update when another protocol update is scheduled, where neither update seemed to happen. Check if this is reproducible.
On attempting to reproduce this, it seems that the issue is not that the protocol update does not occur, but that the new protocol update is not logged.
I noticed a possible issue when scheduling a protocol update when another protocol update is scheduled, where neither update seemed to happen. Check if this is reproducible.