How to troubleshoot Response Time - Instance - RESPONSE_TIMESummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } This article will help in troubleshooting and identifying transactions causing high instance response time. If you have a UI transaction that is taking longer to complete than you would expect, follow the steps outlined in this article to identify the cause. If a user triggers a transaction that executes for a long time, the transaction quota rule will cancel the transaction after 5 minutes (default). You may receive a warning message similar to Your transaction has been cancelled with a reason of Maximum execution time exceeded. This transaction should be investigated using the steps below. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All IO releases Instructions<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The investigation can then focus on the "slow" area of the platform whether it be ACLs, business rules, database, or client-side. All the timings for the individual components are recorded in the Filter Navigator > System Logs. Step 1: Identifying the duration of impact. In Instance Observer, go to the Performance Tab -> Transactions / Response Times. Select the impacted instance. Enter a date like last 24 hours or last 3 days. Select Node Types -> All. Click on get snapshot. Step 2: Analyzing graphs to find out anomalies. There could be an increase in User Transaction Count, which could suggest that the user has to reload, as the page might have timed out. Stacked time (server / network / browser) graph will help identify where the transactions are taking most of the time. Step 3: Identifying transactions that are contributing to the slowness. Go to Stacked time (server / network / browser) graph and click on Transactions Tab -> Slow Transactions. This will redirect to the instance and open the Slow Transactions page. Filter with the userID and time of impact. This will give a result set of all transactions that the user performed during the time of impact. Sort by Average execution time from high to low. Click on the longest running transaction, this page will list slow in ACLs, business rules, database, or client-side. The field that has the high time is the primary contributor to the slowness. This page will also show the example URL which can be used to reproduce the slowness. Step 4: Reproducing the slowness and gathering logs. Login to the instance. Filter Navigator > System Diagnostics > Session Debug > Enable All (This should open a debugging tool in a new window)Reproduce the transaction by using the example URL from the previous step.Review the output in the session log window There are some useful features in the session log - you can download the log, clear the log, or even amend the Filters if you want to remove any noise or clear the output screen. The important word to search for in the log output is EXCESSIVE as those are the slow queries that need to be investigated. If you have an expensive SQL query like the below screen show shows (8.459 seconds), then you can try the index suggestion index feature. In your main UI window where you reproduced the transaction, scroll down to the debug output under the 'Query' header. Now open the record which is the expensive query - this will open a record in the slow query module. Now follow the Index Suggestion Engine article KB0782916 - How to create indexes using the Index Suggestion Engine (ISE)Depending on where most of the transaction time is being spent, that should be the focus. It is pretty self-explanatory - if most of the time is spent processing ACLs, then that area should be the focus. If UI Action time is high, then UI Actions should be investigated. If SQL time is the highest, the database queries need to be reviewed etc. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } KB0782916 - How to create indexes using the Index Suggestion Engine (ISE)