Loop checking in V 8.2 and 16.2

Member for

21 years 7 months

The options [progress override, retained logic ...] to solve out-of-sequence progress are intended to let the software by-pass the loops using different rules; it does not eliminate the out-of-sequence progress loops until you fix the logic.

With progress override or retained logic you may have loops, all shall be identified, so new version can be fixing this issue. 

Member for

16 years 9 months

Using progress overide or retained logic isn't my decision, it is the client's decision.  That doesn't answer the question why 16.2 lists the loops in the sched log when 8.2 didn't. Since the sched log is submitted to the client with the update probably not a good idea to submit it flagging loops, even if they did exist in 8.2 as well.

Member for

16 years 3 months

there is your first mistake never ever ever use progress ove ride. It does not matter what version that you use once an activity is completed it is no longer considered or the forward and backward pass. Why would it ? It does not need any dates becasue you have actuals.