What is Session wait / Session Syncronisation?DescriptionBy design, the platform implements 'session synchronisation' which means that for each user , the platform will only process 1 transaction at a time (per user).This is implemented to prevent 1 user from causing large instance performance issues by triggering multiple transactions concurrently and using lot of node and database resources.ResolutionFor example, if a user were to open multiple browser tabs at the same time with each displaying a list/homepage/dashboard etc, the browser tabs will load the data on each tab synchronously - one at a time. This is session synchronisation in play. How can I view session sync? Via the Instance UI Filter Navigator -> 'client transaction' logsmodify the list to add in the 'session wait time' column (if it is not listed).filter out the transactions for the user that you are interested in, and sort the transactions in chronological order (Created). Via the localhost log files on the application nodes (this may help KB0997495) If you see a user transaction that has high 'session wait', then you can see as per the screen shot below, that this transaction processed really fast (0.008ms) & SQL time is 0.001ms. The key figure here is the session wait time which is 9.8 seconds - which means this transaction had to wait almost 10 seconds for the previous transaction to complete, before it itself could execute. In scenarios like this, the users of the instance need to understand how session synchronisation works, and need to be aware that this can come across to the end user as a 'slow instance', but instead this is expected behaviour. This feature exists in the platform to prevent a single user from consuming all the available resources on an application node.