I have had this happen to me before but on an old version. It would skip some automation jobs in the master job and not send any error messages or anything to indicate that something went wrong. I also had to set up the logging so all of the called jobs did not truncate the log file. I did not experience steps running out of order, it may appear that way because of jobs getting skipped but it does not go back and start an earlier job later. Wish I could remember the version and the fix, I was at a different company when this happened. I am guessing 2.8 or maybe 2.8 was when it was fixed? Sorry I can't be of more help. What version are you running?
↧