Requirement rules not picked by Rule Assembly without Revalidate & Save
Requirement rules from CLM/KYC framework are most often not picked by Rule Assembly post deployment. Revalidate & save is mandatory for every release and even in Production post clear cache restart. When there are more rules, this action can take couple of hours to complete. This necessity is only observed with 'Requirement' rules and not with other general rule types. Can we understand why System could not pick the latest deployed requirement rules in first instance?
@pands2Hi, This might be due to how the system handles caching and rule versioning. When a rule is deployed, it might not be immediately recognized by Rule Assembly because the system is still using cached versions of the old rules. The "Revalidate & Save" action forces the system to refresh its cache and ensure the latest deployed rules are loaded. This step is particularly necessary for 'Requirement' rules because they may have dependencies or specific processing that requires revalidation, unlike other rule types that may be processed more easily. As a result, after clearing the cache, this action ensures that the most up-to-date rules are applied, but it can take time when there are many rules to process.
@SairohithThanks for the response. I have also raised an incident to understand why specifically requirement rules hold this strong dependency to Revalidate after every deployment.
For rest of the rule types including KYC Types from CLMKYC, it is on-demand action.
Let me know if you see any specific reason causing this behavior to requirement rules.