When you run for example a transaction and you see that it’s slow, and you want to identify what query execution is slow in your transaction, you have a very powerful feature that can help you in the slowness troubleshooting : this feature is Session debug
I will explain step by step how to use this feature :
1-Enable session Debug
Go to “System Diagnostics” > Session Debug and click on “Enable All.”
The Script Debugger will open in a new window :
2-Run the transaction
Go back to the ServiceNow instance , and run you transaction :
As an example let’s open the list of all records in incident table :
(Refresh the window if your transaction was already open before the activation of the Session debug)
3-Session Log analysis :
Go the Script Debugger window
You will see that the system logs all actions to perform your transaction .
Search for queries that takes more time to execute .
In your ServiceNow window scroll down and open the Query Module :
If the highest execution time is on ACL then you need to focus on ACL , if the execution time is on a Business Rule or execution of script , notification … then you need to focus on that .
-Disable the debug session Log :
Go to “System Diagnostics” > Session Debug and click on “Disable All.”
Good one!
☑️ Please mark responses as HELPFUL or ACCEPT SOLUTION to assist future users in finding the right solution....
