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.
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.
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.