SLA timeline for records with large audit history can take a long time or run the node out of memory - Known Error

SLA timeline for records with large audit history can take a long time or run the node out of memory Description For records with large audit history (more than 1000 updates), clicking on Show SLA Timeline can take a long time and eventually the transaction may get cancelled. It can also result in the node to run out of memory.

Retrieving the SLA Timeline by sending a request to the Task SLA Timeline API Endpoint can also result in the same.

API Endpoint: https:// .service-now.com/api/now/sla/timeline/{taskId}

Steps to Reproduce

User Interface:

Open a task record which has more than 1000 updates. Scroll down and click on 'Show SLA Timeline' API:

Open REST API Explorer From the API Name dropdown, choose SLA (Internal API) Select Task SLA Timeline Paste the sys_id of a task record which has more than 1000 updates. Workaround The workaround involves adding a check in the script include SLATimeLineV2SNC to display an error message instead of waiting until the request times out when the record has been updated over a certain limit, e.g. 1000.

Open the script include SLATimeLineV2SNC. Scroll down to the function _apiPreConditionsCheck. Add the below if condition at the end of this function. // Need assess a feasible mod count value to attempt the display of timeline. if (taskGr.getValue("sys_mod_count") > 1000) return this._returnApiSecurityError(gs.getMessage( "The timeline for this {0} cannot be displayed because its audit history is too large.", taskGr.getRecordClassName())); This problem is currently under review. You can subscribe to this Known Error article by clicking the Subscribe button at the top right of this form to be notified when more information will become available.