Hangs on Cleaning up Temporary Files

I had a similar issue - the system would throw an error when I tried to publish for HTML5 with Flash fallback. I have mp3 audio on each slide and turned each off one at a time and tried to publish. Turns out it was two out of the 13 audio files that were causing the error. 

On closer inspection, the audio was fine, but the .vtt files created when captions were typed in were somehow problematic. When those were deleted and re-typed, the whole thing worked as planned. 

Not sure if there is a way to create a detection system within the publish or caption writing system, but an alert about problematic caption files would have been useful. When I checked the .vtt files with an online validator, there was no difference between a working one and one that was causing the problem so...not sure what the real problem was, but the .vtt files were the cause. 

Hope that helps someone.

Thanks for popping in to share your experience and findings Sub!

With Articulate Support's assistance, I determined there was an image on one of the slides that caused the Cleaning up Temporary Files process to get hung up.  By publishing a few slides at a time, support isolated the slide with the corrupt image.  I replaced the slide and image and the course successfully published. 

Sometimes you can figure out what slide Articulate's publishing process is having troubles with because it will distort something on the slide, like add a blank shape, etc..

Totally disappointed.  Followed instructions to de-install and re-install.  Absolutely hate this program but I have not other choice.  I've spent thousands of dollars and hundreds of hours and it's absolute garbage.

Hi Steven,

I see you're working with Joshua on this issue to narrow down what's occurring in those Presenter projects! You're in great hands, and I'm following along too. It sounds like quite a unique scenario, so we'll be with you every step of the way to get to the bottom of it. 

One thing that would be awesome is if the publishing processor could give you a more detailed log of what it was doing. E.g. indicate which slides it has processed successfully as it works. Then it would be a lot easier to narrow down where it got stuck.

Hi Will, 

I appreciate the added insight into receiving a publish log to see more detail. I’ll be happy to pass your thoughts on to our product team, but you can also feel free to detail them more through a feature request! 

I am also having the same problem. Tried everything listed in the forum but nothing works. Whats the point of paying for this software. I think ill shift to ispring which has better support and reliable software.

Hi Vinil,

Sorry to hear you're coming across the same issue! If you've tried the solutions shared above with no resolution, we don't want you to continue spinning your wheels alone!

I've opened case on your behalf to connect with one of our support engineers to get to the root of the issue. It seems we've been able to troubleshoot with multiple community members in this discussion and would love to help you out as well. Be on the lookout for a response!