Separate browser tabs do not behave independently leading to navigation activity in one tab affecting navigation activity in the other tab. Issue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms When a user logs in (just once, only creating one session), and then opens up a second tab or window, the navigation activity from one tab will affect the navigation activity on the second tab. The user may experience interfering navigation sequences when using the ServiceNow back button. The same problem occurs If the user logs in multiple times in different tabs or windows (creating multiple session IDs) Release All Cause The ServiceNow back button uses the cache memory stored in the user's machine, therefore it doesn't make a distinction even if there are different session IDs active. Resolution To avoid this, the user can use the browser's back button instead. Alternatively, if the user still wants to use the ServiceNow back button, they can use a private browsing session window in conjunction with a normal browsing session window.