OOTB Agent DisableDormantOperators not working
Hi All,
Our OOTB Agent DisableDormantOperators is running but isn't disabling any users.
If I turn on debug logging and run the activity manually (pzDisableDormantOperators) I can see it goes through the motions but doesn't actually disable any users.
In the activity it's calling this
((PegaAPI)tools).handleEnableOrDisableOperatorRequest(responsePage,operators,paramPage);
But I can find no reference to it and no matter which logger I enable ALL against I get no further information.
Does anyone know what the problem might be?
This isn't working in any of our environments, we are running 7.31.
I should mention that using the PegaAPI method /users/disable works just fine.
Updated: 4 Feb 2021 5:00 EST
Virgin Media
GB
Number of days of inactivity set to 60
Have a number of users in the exclusion list.
Can't share the trace as it's 1.25GB and 128MB compressed. One thing I did notice is that it's disabling (rather saving) some as I can see 776 users changed (pxcommitdatetime) during the run but there are 1187 in total.
What I don't understand is why it's selecting every user within this time period. Surely it should only be selecting users that are not yet disabled, which would reduce the list significantly 178.
UPDATE I've just done a private edit on pzDisableDormantOperators and changed the Obj-Browse selection to only include none disabled operators.
This run has removed the remaining dormant operators. So this suggests there is an issue with the OOTB activity when there are lots of users. Thoughts?
Having looked at last nights run in production and checking the database, I can see that only 749 users were (saved) disabled out of 2431 which incidently happens to match the maxUserCount in the activity.