Uncaught (in promise) Error

ScottG

vgayraud

JeffDavis
 

Tagging you guys since you’re active and helpful!

@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.

In my earlier response, I called this problem harmless because it appeared that only a small percentage of users were affected.  I’d like to clarify:

*I wish that Qualtrics would get off their rear ends and apply some energy and effort into addressing this.  Notice that they were totally silent during this whole exchange, and we provided them with free QA services, and they didn’t even really seem interested or motivated to help out.  I guess they were too busy collecting payments from users.

*I now see that Qualtrics used the Client Side error excuse as a cop-out.  They could have easily done more.

*Speaking of, we caught Qualtrics asleep at the switch.  The general public doesn’t know about this torrent of errors in the background.  It’s only becasue of FullStory that they got caught.

*This incident hurts Qualtrics because customers’ developers and technical staff can now see that Qualtrics is one of the top generators of errors in a browser.

*Even if a small percentage are affected, that still translates to large numbers for a high-trafficked website.   

*I called this problem harmless because I assumed it broke the survey rather then broke the webpage.  My evidence was viewing web sessions in FullStory.   This is a dangerous assumption because I viewed about ten web sessions, and that’s not enough to get confidence.  I would have liked some experts to weigh in.

*I found that this problem creates huge amount of needless noise and makes it harder to find other problems.

If others find this problem or have more info, please add a comment.

Yeah we were also told it was a client side error, but I totally agree. It creates a lot of noise in our console and it is likely an easy fix on their end.

Hi there, ​@c.rose and ​@preichow -- I read through this thread, and I am so sorry for any confusion or frustration the errors may have caused, as well as any unnecessary stress caused by communication gaps.

​@c.rose, I will email you shortly to get more information about the support ticket you filed. 

​@preichow, I would be happy to start a conversation with your account managers regarding your feedback here on the Community, and will kick that off today. 

Again, please accept my apologies; I am committed to providing you both assistance to address current and future concerns. 

​@Michael_Cooksey  No worries about this, especially before the Holidays   I'd be willing to regroup after Jan 1. I appreciate your responsiveness, which shows your customer dedication, and thank you so much!

Hello, ​@c.rose and ​@preichow -- Checking in with a quick update to let you know I reviewed the initial support ticket, as well as the linked escalation ticket that was sent to our resolutions team. 

The resolution engineer commented with the following (excerpt from ticket):

“The error "Uncaught (in promise) Error: Loading chunk [x] failed" is an error that occurs when there is a network issue on the end-user's device.”

​@c.rose -- I mentioned in my follow-up email to you that I did comment on the escalation ticket, asking for more information about the “chunks” so we can learn more about what that might be. Since we are so close to the holidays, many employees are already out of the office, so we may not hear back as quickly as we normally would, but I will stay on top of things. 

Hope this info is helpful in the meantime! Feel free to tag me or ​@AlonsoC with any additional questions or concerns.