How to handle 401 due to inactivity or user logs out from other window


We have simple application page with custom widget that uses typeahead with http to fetch data. Everything works great as long as session is valid. However typeahead stops showing results (as expected) after 401 but UI remains same.

Browser source changes html page back to login form after 401 but doesn't refresh on its own. As a result user is not informed about invalid session.

Any suggestions how to handle this issue.

Bav Systems

Problem 401 starting a new case in chrome browser


I have a 401 error when I start a new case from any process, this problem is to disallow the starting of any new task. Looking the trace of the requests APIs in chrome browser console, I realize the call to an API is triggering this error and the URL is this one: