07/11/2023 09:08 AM
Hi Team,
we are trying to lunch campaign for mover by using user update rule.
When we are trying to run the job to launch the campaign ,it is failing with below error
Log Details
If Team could help me to know, how I can fix this
07/11/2023 10:56 AM
Is the campaign getting launched if you do it manually from Attestation module with the same config and for same set of users?
07/11/2023 08:48 PM
Hi Devang,
Yes, It is working if I create the campaign in Attestation page and Launch it with query as well.
But from rule, it is not working now.
While testing I created multiple rule ,after that I inactivated all test rule and activated a final single rule.
After investigation I realized that Saviynt rule job is launching the campaign for inactive test rule only.
I just feel like, when I was testing with test rule ,Saviynt has stored the values in catch and keep on launching the campaign when ever I'm running the job.
But for the final active rule, It is failing to launch with that SQL error.
I already restarted the system.
How We can clean up if there is any catch present.
07/11/2023 09:11 PM
Hi @PuspanjaliM ,
Logout and close the browser. Then try it in another browser or in private window.
07/11/2023 09:50 PM
Hi Paddy,
I tried your suggested solution, but still, the job is failing.
However, I'm asking for clearing the catch DB server if any are present.
Since yesterday, there has been no update performed on the user attribute, but if we are running the rule job, then it is creating a campaign by using an inactive rule detail.
I'm not sure, but, as per my understanding, if the rule is inactive, then Saviynt shouldn't take action on it.
That's why I thought the catch of an old test might cause an issue.
07/11/2023 09:58 PM
It seems data issue 83.76, Please find actual query in logs
07/12/2023 12:55 PM
If it is performing actions for inactive rule then it might be a bug.
07/12/2023 12:22 AM
Hi @PuspanjaliM ,
May I know the rulekey of this user update rule?
07/17/2023 03:10 AM
Hi Team,
Thank you for support.
I kind of created multiple dummy rules with the same condition and tried to launch a campaign for the same application for the same user.
This issue has been resolved now. I changed the condition of all dummy rules.