Issue found at lesson 100 while connected and attempting to submit answer. The system displayed: 'Error: Your lesson attempt has expired. Click 'New attempt' to start fresh.' This prevented submission of the answer. Please investigate the session timeout or submission handling for this lesson.
Issue found at lesson 100 while connected and attempting to submit answer. The system displayed: 'Error: Your lesson attempt has expired. Click 'New attempt' to start fresh.' This prevented submission of the answer. Please investigate the session timeout or submission handling for this lesson.
Resolved -- Root cause: after a successful lesson submission consumed the attempt token on the backend (Redis removes it), re-submitting used the stale token causing "expired". Added requestNewAttempt() call after successful lesson completion in the auto-mark effect, so a fresh token is always ready.
**Resolved** -- Root cause: after a successful lesson submission consumed the attempt token on the backend (Redis removes it), re-submitting used the stale token causing "expired". Added `requestNewAttempt()` call after successful lesson completion in the auto-mark effect, so a fresh token is always ready.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Issue found at lesson 100 while connected and attempting to submit answer. The system displayed: 'Error: Your lesson attempt has expired. Click 'New attempt' to start fresh.' This prevented submission of the answer. Please investigate the session timeout or submission handling for this lesson.
Resolved -- Root cause: after a successful lesson submission consumed the attempt token on the backend (Redis removes it), re-submitting used the stale token causing "expired". Added
requestNewAttempt()call after successful lesson completion in the auto-mark effect, so a fresh token is always ready.