3662177 - Details to collect for Timeout related scenarios

This article outlines the details that needs to collected for any abnormal timeout related scenarios. 

SAP Sales and Service Cloud Version2 

1) Log on to the V2 tenant on Google Chrome and then change the URL by adding the parameter : ?debugMode=true
Ex: https://<Tenant_URL>/?debugMode=true

2) Open the developer tools, navigate to Network trace and keep this window in a minimized state. (Refer the KBA : Steps to capture Network Trace and Console logs).
3) Continue the usual work and capture the Network trace when the session timed-out. 
4) Provide HAR file after the issue happens.
5) Along with that, following details are Good to have:
   
   a) User ID and Role details along with the Auto Sign Out settings maintained in the Appearance and Behaviour option.
   b) Were Multiple tabs kept open during the time-out.
   c) Was the tab in which application was opened inactive for a long duration or was it being actively worked upon?
   d) Did the user lock the system and went away while being currently logged into the system?
   e) Login method is SSO or Non-SSO. 
   f) In case, SSO, did the user use "sign in using SSO" button or direct URL. Kindly provide the URL if the URL is being used.

KBA , CEC-CRM-SHL , Shell, Navigation , Problem

SAP Sales Cloud and SAP Service Cloud Version 2 all versions