ACL said '= false RULE = Evaluated from cache'

MugTm09 · a month ago

ACL said '= false RULE = Evaluated from cache'.

ServiceNow always evaluates OTB ACL records first, so we added a custom role to this OTB record.

In this record, 'Requires role' is set to 'sn_problem_read'.

(I understand what it means to add something to an existing ACL design. Probably.)

However, the ACL rule was rejected due to an unknown error.

I felt that ACL was not being properly evaluated.

Does anyone have any information about this message?

Unfortunately, 'cache.do' didn't have any particular meaning.

Community Alums · a month ago

Hi @MugTm09 ,
The message means the ACL result came from cache, not a fresh evaluation. Since you modified the OOTB ACL, the issue may be due to cache or role assignment. Try clearing cache and confirm the user has sn_problem_read. If it still fails, review system logs for ACL evaluation details.

Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.

View solution in original post

FasihaM · a month ago

Hi @MugTm09 ,
The message means the ACL result came from cache, not a fresh evaluation. Since you modified the OOTB ACL, the issue may be due to cache or role assignment. Try clearing cache and confirm the user has sn_problem_read. If it still fails, review system logs for ACL evaluation details.

Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.

Community Alums · a month ago

Hi @MugTm09 ,
The message means the ACL result came from cache, not a fresh evaluation. Since you modified the OOTB ACL, the issue may be due to cache or role assignment. Try clearing cache and confirm the user has sn_problem_read. If it still fails, review system logs for ACL evaluation details.

Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.

MugTm09 · a month ago

Hello @Community Alums .

I gave up initially, but tried re-implementing it the next day—and it worked without any issues.
As you suspected, it seems the problem was likely caused by caching.
It was difficult to reproduce the situation, and the conditions under which it occurred were unclear. Also, it's still uncertain why the cache deletion via cache.do yesterday didn’t produce the intended result.
The issue occurred in PDI, so if anyone has successfully handled it through some specific operation, it would be helpful to have that information.

MugTm09 · 2 weeks ago

Hello, Everyone.

In some cases, it may be necessary to clear the browser cache on the user's device.

However, it does not appear necessary to clear cookies.