Hi,
I have a use case where I am getting sudden update(within 2-3 seconds) of a particular column multiple times, Due to this job is triggering multiple times and they are going in frozen state due to update request for the same column of a particular record, hence resulting in error "object was changed by another instance".
To handle the above situation I used retries but sometimes its resulting in the incorrect data setting as jobs are not executing in the exact order as they came in. Again I changed my approach and added a new process step using sql not exists component that will wait if there is any job with the same job name currently executing(true, loaded, false or processing state) also having same Xobjectkey. But its resulting in a deadlock and no jobs will execute as when ever they try to execute they find a job in true state, and they eventually go frozen.
Is there any way I can handle this without jobs going into deadlock?
Thanks
