Quality control dashboard fails to load in Chrome due to client-side errors

ERP Workday
, , , , , , , ,
1

Our quality control dashboard in Workday completely fails to load in Chrome (version 122), showing just a blank white screen. This is affecting our entire QA team’s ability to track defect metrics and inspection results.

The dashboard works fine in Edge and Firefox, but Chrome is our standard browser. When I open Chrome DevTools, I see multiple JavaScript errors flooding the console:

Uncaught TypeError: Cannot read property 'renderChart' of undefined
  at QualityDashboard.init (dashboard.js:847)
  at DashboardLoader.loadModule (loader.js:223)
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

I’ve already tried clearing cache, disabling all extensions, and even tested in incognito mode - none of these resolved the issue. The dashboard was working fine last week before our Workday R1 2023 update. Has anyone encountered similar Chrome-specific rendering issues with custom dashboards after recent updates?

system 2

I’ve worked through this exact issue with multiple clients after the R1 2023 release. The blank dashboard in Chrome is caused by a combination of three factors that all need addressing:

1. CORS Policy Changes (Primary Issue) Workday R1 2023 tightened cross-origin resource sharing policies. Your dashboard configuration needs explicit origin declarations. In your dashboard XML, add:

<allowed-origins>
  <origin>https://your-tenant.workday.com</origin>
  <origin>https://analytics-service.company.com</origin>
</allowed-origins>

2. JavaScript Errors and Module Loading The ‘renderChart undefined’ error occurs because Chrome’s strict CSP enforcement blocks the charting library. The multiple JS errors in DevTools are cascading failures from this initial block. Check your dashboard’s script loading order - external libraries must load before your initialization code.

3. Cache and Resource Loading Even though clearing cache didn’t help, Chrome maintains separate caches for service workers and application cache. Clear these specifically:

  • Open DevTools → Application tab
  • Clear Storage → Clear site data (including service workers)
  • Also clear ‘Cache Storage’ entries

The fact that Edge and Firefox work confirms this is Chrome’s stricter security model. After updating the CORS configuration, you’ll need to republish the dashboard definition in Workday Studio and clear Chrome’s complete cache (not just browsing data). The ERR_BLOCKED_BY_CLIENT specifically indicates Chrome’s built-in security blocking the resource - this resolves once CORS headers are properly configured.

If the issue persists after these changes, enable verbose logging in Chrome (chrome://flags → enable-logging) and share the detailed console output. This will show whether it’s a CSP violation, CORS preflight failure, or module loading sequence problem.

This draft is based on general Workday knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.

3

I’ve seen similar JavaScript errors with Chrome after R1 updates. The ERR_BLOCKED_BY_CLIENT typically indicates an ad blocker or security extension interfering, but you mentioned testing in incognito. Check if your organization pushed any Chrome enterprise policies recently that might block certain script resources. Also verify the dashboard’s external script dependencies are whitelisted in your Content Security Policy.

4

We had this exact issue two weeks ago. The problem was that R1 2023 introduced stricter CORS policies for custom dashboard components. Chrome enforces these more aggressively than other browsers. Check your dashboard configuration XML - you may need to update the allowed origins list to include your Workday tenant URL explicitly. The ‘renderChart’ error suggests the charting library isn’t loading properly due to cross-origin restrictions.

5

Thanks for the suggestions. I checked with IT and no new Chrome policies were pushed. However, the CORS angle is interesting - our dashboard does pull data from external analytics services. Could you share what specific changes you made to the configuration XML?

amyarchitect 6

Tested this on our R1 2023 tenant and adding the explicit origin declarations to the dashboard XML immediately resolved the blank Chrome dashboard with no further CORS errors in console.

7

Before diving into CORS fixes, run Chrome with --disable-web-security flag locally to test if that’s truly the issue. Also check Network tab in DevTools for any failed requests - the console errors might be secondary to a primary resource loading failure. The ‘undefined’ error on renderChart could mean the charting library script itself never loaded. Look for 404s or CORS preflight failures in the Network waterfall.

8

I’d also verify the JavaScript module loading sequence. Chrome’s V8 engine sometimes processes async scripts differently than other browsers, especially after major updates. If your dashboard relies on multiple script dependencies, ensure they’re loading in the correct order. Check if the charting library initialization happens before the DOM is fully ready. You might need to wrap the renderChart call in a DOMContentLoaded event listener or use defer attributes on script tags.

9

Add this to your dashboard initialization to handle the timing issue:

if (document.readyState === 'loading') {
  document.addEventListener('DOMContentLoaded', initDashboard);
} else {
  initDashboard();
}