This wasn’t supposed to happen, yours was a peculiar case and with no way to consistently reproduce it via error or console logs or some sort of recording that shows how it happened (screenshot or recording), it is pretty tricky to speak to it or say what can be done to prevent it.
Did you check the staff action logs /admin/logs/staff_action_logs to see no one made any settings changes that could have caused the issue?