Pipeline Refresh Error Causes GRC Tasks Page to Hang in the Edge Browser

[Jay Van]

After a Washington DC Upgrade the GRC Task page hangs in the Edge Browser. An "unable to determine autoflow disable rule" and "dispatching pipeline refresh count in the thousands" is displayed in Edge developer tools. The browser can hang in this state for 10 to 15 minutes. Sometimes a browser refresh will resolve the issue and the content will be displayed. Clearing all browser cache corrects the issue intermittently for new and existing GRC users.  Has anyone experienced the same issue in GRC Tasks page in the GRC Tasks Portal or the Compliance and Risk Workspace Tasks page after a Washington DC upgrade? We are going to also check to ensure our security tooling is not interfering with the client server communication. 

[Community Alums · Accepted solution]

Hi @Jay Van ,

I am also facing the same, i raised a Case with ServiceNow, what i learned is that it seems to be a BUG in the product.

Due to Automatic Refresh Happening in the components in the workspace, this is making the page load late.

Expected Fix is going to happen in Xanadu Release.

[Jay Van]

Thanks Goutham. I'll report back what happens. 

[Jay Van]

A data set was loaded and this resolved the issue.