Critical path not showing correctly

I have predecessors and durations. As seen from my schedule all tasks are linked. However, the critical path just shows the last 3 milestones. Any idea how I could fix this?
Answers
-
I am having this same issue! It was showing the whole critical path correctly a few days ago and then after a few changes it is now only showing the last milestone
-
I am also having this issue on all new and existing sheets.
-
Hi @Raphael, @Stewart Winter, @breso
There was an update made on Friday, the 18th - can you check to see if your project plans now correctly show their critical path again?
Thanks!
Genevieve
Need more information? 👀 | Help and Learning Center
こんにちは (Konnichiwa), Hallo, Hola, Bonjour, Olá, Ciao!👋 | Global Discussions
-
@Genevieve P. - It works now. Thanks for your help!
-
@Genevieve P. - Thank you!
-
I´m having the same issue! Did you guys change anything? @Stewart Winter @Raphael Or it´s just right back ok now?
-
I am also facing the same issue, only able to see few boxes in red for crtitical path, @Genevieve P. can you please take a look
-
It doesn't look like this highlighted task has any predecessors or dependencies (I don't see any lines between it and another task). Are all your tasks connected?
Need more information? 👀 | Help and Learning Center
こんにちは (Konnichiwa), Hallo, Hola, Bonjour, Olá, Ciao!👋 | Global Discussions
-
TL:RD - check the validity of the predecessor(s) on the first item in your errantly short critical path.
I encountered this issue - incorrect, limited critical path - that has been working properly last week. Since then I had made many modifications to the schedule (add/remove tasks, etc) after which my critical path got super short (only 3 tasks). Looking at the first in the now unreasonably short critical path, I realized I had an errant comma following one of the two predecessors for the first task that appeared in the short path, so it looked like a valid predecessor, but the comma prevents the predecessor from linking to the task and also prevents it from displaying a #REF error because of the comma. So it looked like I had a predecessor, but it was not truly making the connection.
Categories
- All Categories
- 14 Welcome to the Community
- Customer Resources
- 67K Get Help
- 441 Global Discussions
- 154 Industry Talk
- 502 Announcements
- 5.4K Ideas & Feature Requests
- 85 Brandfolder
- 156 Just for fun
- 79 Community Job Board
- 512 Show & Tell
- 34 Member Spotlight
- 2 SmartStories
- 307 Events
- 36 Webinars
- 7.3K Forum Archives