Service Operations Workspace is very slow to load in Washington DC

[Jeff Welton1]

Hello Community -

We just went live on Washington DC release and some process users are experiencing slowness loading the Service Operations Workspace (SOW).  Any ideas on what may be causing this will be greatly appreciated. 

Thank you in advance and best regards,

Jeff

[Shivalika]

Hello @Jeff Welton1  

Tbh, Washington was the worst release I have ever come across and that's since Orlando. I mean there were several several several issues and defects left in washington unattended. I remember we had several cases. 

But now we also have Xanadu and even Yokohama is gonna be available for customer instances. Maybe just check in "Slow Jobs" , "Active Transactions that have age >2 minutes and kill them", just clear cache of the instance. For performance slowness these things can be done, else you can raise a servicenow case and they can check if any node has higher database usage than normal and point out something. 

Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket. 

Regards,

Shivalika 

My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194

My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY

[Robert H]

Hello @Jeff Welton1 ,

Which activity in particular is slow? Opening the workspace itself, or performing a specific action or going to a certain type of form?

In general, such slowness issues can usually best be analyzed by someone who has access to the instance, so I would recommend that you open a Now Support case to have someone from ServiceNow check for the root cause.

Regards,

Robert