Scripted user criteria return stale results when the script uses gs.getUserIssue Scripted User Criteria not working when using the gs.getUser function Release All Cause When a scripted user criteria calls gs.getUser, the criteria results are cached after the first run. Later changes to membership are not reflected until the cache is refreshed, so the criteria appears to stop working. Resolution User Criteria are not working when they use gs.getUser in the script.This is because when gs.getUser is used, the scripted User Criteria get cached after running once.If we remove the scripted Criteria and directly add the users, it will workTo avoid this, the customer can use Extended user Criteria Related Links user_criteria,Scripted_getuser_criteria