Session expiry during quiz causes authentication failure and incorrectly inflates the recorded completion time

This appears to be an edge case where the existing session/token TTL may have expired while the user was taking the quiz. The user already had an authenticated browser session and had not freshly logged in today. During submission, the quiz unexpectedly returned a “Not Authenticated” error. After logging in again, all previously selected answers were retained except for one question, which required the answer to be reselected before resubmission. The final quiz completion time appears to include the entire duration from the initial attempt through authentication recovery and final submission, resulting in an inaccurate completion time. Possible Root Cause: The session/token may have expired midway through the quiz due to TTL expiry, causing the submission request to fail authentication. Expected: If the session expires during a quiz, the application should gracefully handle re-authentication while preserving the quiz state, and the completion timer should not include time spent recovering from the authentication failure.

Last updated Sep 8, 2026