servicenow apporvals on "my page portal" suddenly cant be accessed

asd22
Tera Contributor

Hello.

 

I was testing out our approvals that have been working fine as usual for the last months. When suddenly after a refresh the page said "you cant access this approval" i went from our developer instance to our test and there it worked fine, but then suddenly it also happend there and now also the same issue in our production. We havent changed anything as far as i know, there is not a acl issue as we tested this.  Any clue to what might have caused this?

7 REPLIES 7

@Sarthak Kashyap  @Viraj Hudlikar any thoughts on this

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

Hi @asd22 ,

 

@Dr Atul G- LNG , thanks for tagging me, I didn't encounter this type of issue yet, if this is not issue with ACL then I'll suggest to clear the cache, check on incognito mode, do inspect and check console if there is any error is showing. If all these didn't help raise a case with Servicenow.

 

Please mark my answer correct and helpful if this works for you

Thanks and Regards,

Sarthak

KuldeepVaghela
Tera Contributor

If you're absolutely sure no ACLs or Update Sets changed, check your instance patching schedule.

When an issue 'travels' from Dev to Test to Prod like that without manual intervention, it usually implies the instances were patched/hotfixed in that order, or a specific browser update (like Chrome) rolled out to your machine that isn't playing nice with the session cookies.

Also, try clearing the server-side cache (cache.do) on Dev just to see if it clears it up. It sounds like a session or widget caching issue.



Let me know if this works for you. If it does, please mark the answer as Correct/Helpful so others can find the fix.