Description:
During a coding session, the application logged me out due to inactivity despite me being actively engaged in reading and understanding the problem statement. The session timed out within approximately two minutes, which is insufficient for a typical interview scenario.
Following the timeout, I was unable to initiate a new session. The system continued to detect the previous activity, preventing me from restarting and proceeding with the new parakeetai session.
Impact:
This issue is directly affecting my interview process and preventing me from completing the coding session.
Expected Behavior:
The inactivity timeout should be extended to allow sufficient time for reading and thinking during coding interviews.
Users should be able to restart a session without being blocked after a timeout.
Actual Behavior:
Session times out within ~2 minutes of perceived inactivity.
System does not allow starting a new session afterward.
Priority: High (Interview-blocking issue)
Request:
Please investigate this issue and increase the inactivity timeout duration. Additionally, ensure that users can restart sessions seamlessly after a timeout.
Please authenticate to join the conversation.
In Review
Bug Report
About 1 month ago
Get notified by email when there are changes.
In Review
Bug Report
About 1 month ago
Get notified by email when there are changes.