Rule cache problems
During the last weeks we are experiencing more and more issues with rule caching in production.
After some deploys of a new package or in some cases without an apparent cause, the rule cache is not built in the right way and the some rules are not considered, as they were not present in the environment...
Does anyone know what might be the cause of these problems? Have you ever experienced similar issues?
Tata Consultancy Services
IN
Hi @AleMax225,
Could you please refer below articles
https://support.pega.com/question/how-clear-rule-cache
https://support.pega.com/question/rule-cache-management-clear-cache
https://support.pega.com/question/how-clear-caches-81
Thanks,
Ashok
Corner SA
IT
Hi @Bhumireddy,
I am interested in trying to understand what might be the cause of these issues, because I think that there might be an underlaying problem.
We are already using all the API described in the articles to manually solve these kind of issues...
Thanks
Proximus
BE
Hello,
We also faced this from time to time without always finding a clear explanation.
What's not always done:
- Static Assembler for Applications & PegaRule
- Troubleshooting with exact Same AG than the system uses (for background processing for example)
- Checking whether clearing local cache leads to a different result (pegatemp)
- We also directly re-saved the rule in the problematic environment (only for flows, we had to do that and it worked)
- We by-passed this issue by saving the same rule in Production ruleset, Then it was working, looked AG issue in some way
- We re-checked the full applications structure to be sure that all references and versions were pointing to correct ones. (When imported the system is not always complaining, but when re-saving applications it was raising concerns for some references)
- Trying to identify whether it's mostly from same server also. We also faced the ghost issue. All looked fine, no error in logs, or anywhere but not working fine. We restarted the server and it was ok...
Then, there's also the daily db cleanup which also performs some cleaning for the cache also and which is not running by default.
Hope this gives some clues for your investigations
Regards
Anthony