Job Scheduler execution status is showing as fail and fail log messages written to logs even one obj-open lock fails out of 1000
We have job Scheduler which loops on 1000 records per execution and opens each work object using obj-open-by-handle then do some update according to business requirement.
Suppose if one work object at 10th iteration encounters a locking issue we have an exception handling and custom log messages on obj-open-by-handle in place so remaining records will be executed without any issue.
But the overall job execution is showing failed and log messages are logged for job failure even remaining 999 record execution is success
Ideally the job should consider overall status right? Please help me understand the mechanism.