Tasks with >zero slack showing as critical path (MSP 2013) 1

[tmawhinney]

Hi -

I'm new to this forum, I hope someone can help.

I am working with a schedule recently built in MSP 2013 that has many >zero slack tasks showing as critical. This is my first time using MSP 2013 (I am an advanced user on earlier versions).

I've analyzed the settings for the usual suspects and see no obvious issues. The schedule is simply structured with mostly F-S, ASAP logic and summary tasks to keep tasks organized. There a few tasks that are ALAP, but when I removed these, there is no change to this odd behavior.

Any suggestions would be greatly appreciated.

Thanks, Todd

 

[tmawhinney]

Well ... I found the culprit ...

Some of the tasks were marked as manually scheduled tasks. In one case a high-level summary task was created this way and all tasks affected were within that summary task. Once I changed it to automatic, this problem went away.

Todd

 

[JulieInMaine]

Thanks for posting the solution, Todd. With luck it will help someone else.