Why did the change order workflow restart automatically?

If the schedule processor job is stuck in the initial run and it doesn't require any user intervention, the application restarts the job. It restarts up to 5 times with increasing time gaps in between each job.

You don't need to manually search for unsuccessful change orders that weren't processed due to locked affected objects.

Note:

An item can be simultaneously updated from different sources. A record can be updated through the user interface, while another update could be triggered through a web service or scheduled process. This results in locking issues, and the jobs can't be complete successfully. In such scenarios, the application restarts the subsequent job after some wait time and attempts to complete the job.