You could only do this at the time of processing the job. So you would need to have the job check for updates and changes stored somewhere before it ran the rest of its code.
Or work out a way to delete that job before it starts and queue a new one.
As most jobs have a delay before they run it is likely that most jobs should check in some way before they execute that the state is still the same. This is also why keeping jobs to as smaller item of change as possible helps.
Sign in to participate in this thread!
We'd like to thank these amazing companies for supporting us