Major Performance issues after Washington upgrade

[Brenda Williams]

We upgraded to Washington and have had major performance issues that continues to bring one of two nodes down causing an outage to our customers. They have pointed to the keySet function call from the getAllUserCriteria method. Is anyone else using this method on their Service Portal and on Washington version? Are you experiencing issues or just fine? We had support tell us to change from SNC.UserCriteriaLoader.getAllUserCriteria() to sn_uc.UserCriteriaLoader.getAllUserCriteria()  saying the SNC.User one is deprecated. We made the change and still are having issues and now support is saying the sn_uc.user one is also deprecated though that's what they said to change to. Anyone using any other type of API call to get user criteria?

[Khanna Ji]

Hi Brenda - Were you able to solve this? Please help us.

[Brenda Williams]

Hi Khanna,

Yes we did resolve it but it required us to Remove or comment out new sn_uc.UserCriteriaLoader.getAllUserCriteria() everywhere we had used it throughout or portal/catalog. Rewrite meetsCriteria() to use $sp.canReadRecord(now_GR) or $sp.canReadRecord(table, sys_id)

[johnmark]

UserCriteriaLoader.getAllUserCriteria() method is a deprecated method and we advice using userMatches() instead.

☞ Please refer to this article below, which explains on this in detailed.
https://www.servicenow.com/community/now-platform-blog/a-deep-dive-to-user-criteria/ba-p/2281285

Below are additional Knowledge articles which discusses Semaphore Exhaustion caused by the getAllUserCriteria function being called in widgets:

Semaphore Exhaustion is caused due to the getAllUserCriteria function getting called in widgets

Semaphores keep getting stuck and cause slow performance due to UserCriteriaLoader.getAllUserCriteri...