We had a task that started on Friday at 1700 when it should have started on the following Monday at 0800. The duration ran through Saturday and Sunday (non-working days). There were no resources assigned and no calendar issues. We “fixed” the problem by zeroing out the duration and then re-entering the same duration value. After doing that, the task moved to start on Monday. Problem solved, but we don’t know what caused it. The duration on the Gantt view was shown as running through the weekend, but the finish date was still correct, so Saturday and Sunday were not actually being counted as workdays even though the Gantt chart showed the task spanning the weekend. It’s a large schedule and this problem occurred on multiple tasks – any insight into the cause would be appreciated! Maybe just a glitch?
Tim, I’m not sure how the task started at 1700 but that could be a fluke with the actual time a predecessor ended. You can do some further analysis next time by changing your date format (File / Options / General) to a date and time format and see exactly what is driving the task. The Gantt bar is normal behavior. If the task started on Friday then the bar will span the weekend by default. Hope that helps…
Very helpful! Looks like it was related to the actual time the predecessor ended. Before I posted, we had already selected the date/time format in Options to see that the task was starting at 1700 on Friday instead of 0800 on Monday. Based on your suggestion, I created a task that ended on Friday and had a successor starting on Monday. When the Friday task had a full 8 hours planned, the successor started at 0800 Monday without showing the Gantt bar running through the weekend. When I changed the 8 hours to 6.5 on Friday, the task ended at 1530 on Friday and the successor started at 1530 on Friday and the Gantt bar ran through the weekend. Much appreciated.