I have business scenario where dispatcher should run every 5 min, but due to machine allocation, trigger goes to pending state but as 5 min is very short duration meanwhile another job gets triggered for the same job, sometime this keeps on happening pending count increases affecting other Bot timings and schedule misses
I want to avoid this situation, I just want any one of these jobs to run, when the same job is in pending I don’t want to trigger the same job again
@Ishwar_P_S , you probably have to attack this from a few different angles.
Assign a lower priority for time triggered jobs. This would help to process other jobs with higher priority, e.g. queue triggered jobs
Modify the time triggered process in a way it checks for any pending jobs off the same process when it starts up; proceed with the job only if there are no pending ones. This will not avoid the issue completely, but would help to end duplicate jobs within seconds.