Loop checking in V 8.2 and 16.2
I have been previously running 8.2 using progress overide on the programme. Occasionaly I have inadvertantly added logic that created a loop that was detected and removed from the programme. Otherwise the scheduling wont run.
This month we upgraded to 16.2 and following a normal monthly update and re-plan and many scheduling runs I ran a sched log that detected 28 loops that weren't flagged when running the scheduling.
I removed the loops and the sched log detected no further loops. When I checked the previous month's programme that was updated created in 8.2 in 16.2 it flagged 29 loops in the sched log.
I am assuming that 8.2 ignored loops on completed tasks if using progress overide but I am wondering why 16.2 now flags these in the sched log but not when scheduling?