Skip to main content

Session Timeout Recovery Workflow

When your Polarion session expires due to license timeout or inactivity, Nextedy RISKSHEET provides a recovery mechanism to save your work. Timeout Error Dialog (Version 24.8.6+):

Recovery Steps

  1. When the timeout error appears, do NOT close the RISKSHEET tab or browser window
  2. Click the “Log In” button in the error dialog - This opens a new browser tab
  3. Authenticate in the new tab - Log in to Polarion with your credentials
  4. Return to the original RISKSHEET tab - Switch back to the tab where you were editing
  5. Click 💾 Save - Your session is now restored, and changes will persist
After re-authenticating in the new tab, your session is automatically restored in all other tabs. You don’t need to reload the RISKSHEET page—just save your changes directly.

Session Timeout Triggers

Timeout TypeTypical DurationTrigger
License timeout30-60 minutesConcurrent user limit reached
Inactivity timeout30 minutes (configurable)No user interaction
Server maintenanceVariableAdministrator action

Prevent Session Timeouts

Nextedy RISKSHEET includes a keep-alive mechanism (/api/keepalive endpoint) that prevents automatic session expiration during active editing. Keep-alive behavior:
User ActivityKeep-Alive PingSession State
Edit cellping (every 5 min)Active
Scroll viewping (every 5 min)Active
No activity(no ping)Timeout
However, license timeouts (when concurrent user limits are reached) override keep-alive and force session expiration.

Session Timeout vs. Other Errors

Session timeout errors are distinct from:
Versions prior to 24.8.6 did not provide a clear timeout recovery dialog. Users who encountered session timeouts had to manually reload the page and re-enter their changes. Upgrade to 24.8.6+ for improved error handling.

Verify Session is Active

After re-authentication, confirm your session is restored:
  1. Look for your username in the top-right corner of Polarion
  2. Check that the RISKSHEET toolbar buttons are active (not grayed out)
  3. Try clicking into a cell—you should be able to edit without errors
  4. Save your changes and verify the success message appears

See Also

Support TicketsSource Code
  • RisksheetViewServlet.java
  • GetSetUtil.java