We tried to run an update on our privilege modification job on a specific attribute (GRC-IDM integration) for our non-production privileges. When I found last Friday night that the system is having a hard time running it, we stopped the job and decided that today to modify the job definition to avoid long processing. However as per checking last night in the system, the status of it from last Friday is still the same: "Stopping".
Is there any way that we can forcefully stopped this job from running? It is affecting all major provisioning in non-prod as when trying to search for a privilege or assigning it, the system will throw an error. I am assuming that because the job is locking the privilege entries(?).
Thank you and stay safe.