BUG: Spinning wheel of doom when attempting to log back in after an idle timeout

[ttlenard]

Describe the Bug
A clear and concise description of what the bug is.

This bug is related to #10349. We attempted to fix it with this bug, but it seems that it didn't work?

We have had additional reports that after a user gets the "Are you still there?" modal and they do not click yes, the user is then presented with a never-ending spinning wheel when they attempt to log in after what appears to be that the user has been logged out. The solution is to just click the refresh button and they will get the log in screen.

Business Impact/Reason for Severity
low

In which environment did you see this bug?
Prod, Test

Who were you logged in as?
This was reported to us by a Judge, and I have seen it happen on Test as well.

What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.)
Using the application.

To Reproduce
Steps to reproduce the behavior:

1. Log in to DAWSON
2. Do some stuff (maybe have additional tabs open?)
3. Remain idle for 55 min, receive the Are you still there message, but don't click yes, just let it go
4. System will appear that you are logged out
5. Re-attempt to log in
6. Get the spinning wheel of doom.
7. To get out of it, you just have to click the refresh on your browser

Expected Behavior
A clear and concise description of what you expected to happen.
Users should not have to refresh, when they click log in, they should be able to just log back in

Actual Behavior
A clear and concise description of what actually happened.
Users are getting a spinning wheel of doom and they have to click refresh on their browser in order to log back in after an idle timeout.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Cause of Bug, If Known

Process for Logging a Bug:

• Complete the above information
• Add a severity tag (Critical, High Severity, Medium Severity or Low Severity). See below for priority definition.

Severity Definition:

• Critical Defect
  Blocks entire system's or module’s functionality
  No workarounds available
  Testing cannot proceed further without bug being fixed.

• High-severity Defect
  Affects key functionality of an application
  There's a workaround, but not obvious or easy
  App behaves in a way that is strongly different from the one stated in the requirements

• Medium-severity Defect
  A minor function does not behave in a way stated in the requirements.
  Workaround is available and easy

• Low-severity Defect
  Mostly related to an application’s UI
  Doesn't need a workaround, because it doesn't impact functionality

Definition of Ready for Bugs(Created 10-4-21)

Definition used: A failure or flaw in the system which produces an incorrect or undesired result that deviates from the expected result or behavior. (Note: Expected results are use cases that have been documented in past user stories as acceptance criteria and test cases, and do not include strange behavior unrelated to use cases.)

The following criteria must be met in order for the development team to begin work on the bug.

The bug must:

• Be focused on solving a user problem
• Contain data for all fields in the bug template, so the team can pick it up and begin working immediately

Process: If the unexpected results are new use cases that have been identified, but not yet built, new acceptance criteria and test cases should be captured in a new user story and prioritized by the product owner.

If the Court is not able to reproduce the bug, add the “Unable to reproduce” tag. This will provide visibility into the type of support that may be needed by the Court. In the event that the Court cannot reproduce the bug, the Court will work with Flexion to communicate what type of troubleshooting help may be needed.

Definition of Done (Updated 4-14-21)

Product Owner

• Bug fix has been validated in the Court's test environment

Engineering

• Automated test scripts have been written
• Field level and page level validation errors (front-end and server-side) integrated and functioning
• Verify that language for docket record for internal users and external users is identical
• New screens have been added to pa11y scripts
• All new functionality verified to work with keyboard and macOS voiceover https://www.apple.com/voiceover/info/guide/_1124.html
• READMEs, other appropriate docs and swagger/APIs fully updated
• UI should be touch optimized and responsive for external only (functions on supported mobile devices and optimized for screen sizes as required)
• Interactors should validate entities before calling persistence methods
• Code refactored for clarity and to remove any known technical debt
• Deployed to the Court's test environment if prod-like data is required. Otherwise, deployed to any experimental environment for review.