ScottG

vgayraud

JeffDavis
 

Tagging you guys since you’re active and helpful!

@c.rose What coincidence; I just noticed the same error for the first time while checking out network errors in FullStory.   It means that the browser couldn’t find a needed javascript file. Clear browser cache to resolve.

It’s likely that Qualtrics was unable to reproduce this error because it appears to happen client-side (so their servers have no record of the event).   In addition, the error is caused by unusual browser or network conditions. 

Background:

Chunk Load Error occurs when the browser encounters an error in fetching some JavaScript files, which were dynamically imported. The error can caused by missing or outdated files, or a problem with file integrity; checksum not matching  

Users: If you are encountering this error as a user of an application, the most simple way to resolve it is to clear your browser cache (and also restart it for good measure) and try again

Developers: Since the most common occurrence of this error is when the chunk files are missing, developers can start by ensuring that the chunk files are being correctly served, and the URLs being used to download the chunk files are appropriate.

My errror:

"Unhandled Promise rejection: Loading chunk 10 failed.
(error: https://siteintercept.qualtrics.com/dxjsmodule/10.1ba09bXXXXX.chunk.js?Q_CLIENTVERSION=--blocked--&Q_CLIENTTYPE=--blocked--&Q_BRANDID=--blocked-- ; Zone: <root> ; Task: Promise.then ; Value: Error: Loading chunk 10 failed.
(error: https://siteintercept.qualtrics.com/dxjsmodule/10.1ba0XXXX9692.chunk.js?Q_CLIENTVERSION=--blocked--&Q_CLIENTTYPE=--blocked--&Q_BRANDID=--blocked--    at r.e

@preichow You are correct! They were unable to replicate the issue because it was a client side network error. I also discovered the error through FullStory, that is interesting. My perspective is so long that is isn’t impacting the customers, it is fine. Hopefully it stays that way!

Now that’s too funny! FS shows things we’re never seen before.

Luckily for us, it looks like only a small group is affected, and there doesn’t seem to be loss of functionality, except maybe the survey intercept is not active for that one person. Big disclaimer that I call it harmless based on only a several sessions.  I’m going to keep my eyes open.