This is possible if you opened codedamn in a different tab/window or session timed out, or on some rare occasions, it could be just our fault