Thank you for sharing this bug report; if this happens again in the future the current work around for this issue is to log out and log back into the server.