Skip to main content
New Participant
August 21, 2018
Question

Proofs not loading issues (new and legacy viewers)

  • August 21, 2018
  • 15 replies
  • 2778 views
Is anyone else experiencing issues with proofs not loading in the integrated system? For about 2 months, we have users report that when they attempt to open a proof using the new proofing viewer they get an error "Proof not loaded try again." When using the legacy viewer, the screens opens up to solid gray. If we close the window and reopen, the proof opens fine. I've been working with our Workfront Support person, but he and the development team have been unable to replicate it on their side. I was leaning towards the possibility that it was our network, however I've encountered the same issue at home on my personal computer and network. Workfront suggested it's our network, so I have opened a ticket with our internal IT, however I am curious if anyone else has had the same problem. Side note: this was happening prior to the 2018.2 release. Wendy White AmeriCredit Financial Services, Inc. dba GM Financial
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

15 replies

Employee
March 1, 2024

Our customer is facing the same issue with a browser of Chromium 98.0.

Is anyone still facing the same issue?

New Participant
November 21, 2018
For me, when they turned on the new proofing tool the defaults about which tool would open changed, and then the ability to update the defaults was removed from my instance. I called support and they put the default setting options back in and by experimenting with the variations I was able to get everyone (almost) happy. Nobody is happy that it takes 2 clicks to see an email – because I didn't make the desktop proofer a default as that was causing other issues when viewing a PDF.
New Participant
November 20, 2018
We were able to figure out the issue. In the browser settings, somehow cardinalhealth.com/proofhq was blocked. We were able to unblock the site and everything started working again. We believe this was caused from a browser update. Denver Lemont Cardinal Health
New Participant
November 20, 2018
We are having this same issue in Chrome since Friday, 11/16. However, it is working correctly when using Firefox and IE. A ticket has been opened with Workfront if you would like to reference when you contact Workfront - Support Request #1172788. Chad LeVake Securian Financial Group, Inc
New Participant
November 19, 2018
Was there any update on this issue? One of our user's today is experiencing this issue. Whenever she opens any proof (any project, any version, any doc, new or existing) she is getting the error message "Proof not loaded. Try Again". She is on a Mac and using Chrome. She has been a user for around three years and this has never been an issue. She's restart her computer, logged out of Workfront, we've removed her proof licenses and then reapplied it. Any thoughts? Denver Lemont Cardinal Health
New Participant
September 22, 2018
Thanks for the replies! The cache was my first thought too, Anthony, but the user that complained to me is a front end web dev, and he is clearing his cache many times a day, so he and I both agreed that probably isn't the problem in his case. I didn't realize there was a fix out for this recently, but I suppose it isn't working for us, at least, since the complaint came through this week. I think I may be opening up a ticket soon myself. Mike Perez Tailored Brands
WendyWhAuthor
New Participant
September 20, 2018
Mike, Workfront said they released a fix on 9/11 to resolve the problem. However, we had a report yesterday of another instance. I'm waiting to see if he has anymore and if so to get a screenshot with the Console open so we can see the error message. Anthony, I don't think we tried clearing the cache, but I'll definitely recommend that to the user who has experienced this the most. Wendy White AmeriCredit Financial Services, Inc. dba GM Financial
imgrund
Employee
September 20, 2018
For us, if the user clears their browser's cache, that fixes the issue. :) Anthony Imgrund FCB
New Participant
September 19, 2018
Yesterday, I had a user come to me with this same issue... did any of you find out what the cause was, or find a solution to the issue? I was unable to replicate the issue, so I am leaning toward it being an issue with the user's machine and/or our network, but also hoping I might find some confirmation here :) Thanks! Mike Perez Tailored Brands
New Participant
August 23, 2018
Yep. Same issues and more. Robert Campbell Tractor Supply Company