Home > Overview > Support and Troubleshooting > Statement Analyzer Timeouts
When a user is inactive for a period of time that exceeds the configured timeout limit in Statement Analyzer, the user will see the following message when he or she next attempts to perform an action in Statement Analyzer:
Your session has timed out. You will now be redirected to the Login page.
The user is then logged out of Statement Analyzer and the login page appears. At this point, the user can then log in to Statement Analyzer again.
If for any reason Advisor is unable to return the user to the login page, this message appears:
Baker Hill Statement Analyzer has failed to redirect you to the Login page. Please log out and log back in again.
When a user who is logged in to Advisor or Origination accesses Statement Analyzer, how timeouts are handled depends on how the Statement Analyzer window was opened.
If you launch a Statement Analyzer window from within Advisor (you did not manually log in to Statement Analyzer) and a timeout occurs in the Statement Analyzer window, it will close the Statement Analyzer window and trigger a timeout in Advisor. As soon as the user tries to save or open a window in Advisor, the user is logged out of Advisor and returned to the Baker Hill Advisor Login page.
If you launch a Statement Analyzer window from within Origination (you did not manually log in to Statement Analyzer) and a timeout occurs in the Statement Analyzer window, it will close the Statement Analyzer window, trigger a timeout in Origination, and return you to the Baker Hill Origination Login page.
If you open a new browser window and manually log in to Statement Analyzer while already logged in to Advisor or Origination, timing out in one solution because of inactivity will not affect the solution that you are actively working in.