Service-Now is slow for only one user

jai123
Kilo Explorer

Hello All,

 

Service-Now seems to be very slow for one particular user and for all the others it is working fine. Not sure what might be the reason. He is having same filters as his team members but for all his tem-members it works fine. When try impersonate him and see, then also we can observe the issue. So it is not exactly Internet Issue or Network issue.

 

Anybody knows what might be the reason or if any settings need to be changed, kindly help us.

 

Thanks in Advance

14 REPLIES 14

Subhajit1
Giga Guru

Hello Jai,



The issue seems to be with the Filter itself.


Others might be having the same filters, but the filter output for the affected user might be high which is causing his/her instance to slow down. He might have generated a large amount of records.



You could also tally the user's profile with people having same access levels. Also check the Profile preferences.



Regards,


Subhajit


Actually issue is with his home page. He has few widgets on his home page and every time he load the home page these widgets are not loading and shows cancelled error.



We checked the his colleagues profile who has same widgets on his home page and it works fine.


Hi Jai,


Try removing these widgets from the user's homepage and then re-add them using the Add Content link on the Homepage if you have not done it already.


Also check the roles for the Concerned User in the sys_user_has_role table and see that by any chance any of the concerned users' roles have been deactivated.



Regards,


Subhajit


Slava Savitsky
Giga Sage

The same filter can take longer time to load depending on which column it is sorted by. For example, sorting Incidents table by Created date will work much faster than by Number. So you might want to compare sorting preferences of the affected user to those of other users who do not have this issue. User preferences are stored in sys_user_preference table. The ones that deal with sorting are called table_name.db.order and table_name.db.order.direction.