Project Baselines taking longer to load in New Project Workspace when having more than 3000 tasks<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Description : Project Baselines are taking longer time (approx. more than 3 minutes) to load in New Project Workspace when having more than 3000 tasks linked to a project Steps to Reproduce: 1. Hop onto the instance with Xanadu P9b version2. Open "Project Workspace"3. Open a project that has more than 3000 tasks4. Click on the "Baselines" icon on the top right corner.5. Create new Baseline if nothing available or select the existing baseline6. Click apply7. Notice that the baselines (gray line under the project) takes more than three minutes to load. Workaround : 1. The issue is caused by the OOB script include "ProjectWorkspaceFetchApi"/sys_script_include.do?sys_id=1b9e371677723010132628489a1061312. The 'getBaselineItems' method in the script has to be modified since the !baselineItem.canRead() check can be used only record level acls check is required. if field level acls are not required other conditions can be ignored.3. The above method needs to be modified to include the below under line 428 in the script which should resolve the issuewhile(baselineItem.next()){if (!baselineItem.canRead() || !baselineItem.baseline.canRead() || !baselineItem.start.canRead() || !baselineItem.end.canRead() || !baselineItem.task.canRead()){continue;} Related PRB : PRB1935340