Question bank is crashing my lesson

I'm having problems with a lesson when I add a slide which draws from a question bank. The lesson previews and publishes fine without the question bank, but crashes after I've added it and then try to preview or publish.  I'm using Articulate 2, has anyone else come across this?

The lesson is commercially sensitive so I cant attach on this forum, but happy to send the lesson to Articulate support.

17 Replies
Ashley Terwilliger

Hi Simon,

Thanks for sharing here. I took a look and saw the same as you on my first attempt and importing the entire file into a new project. I instead looked at removing your question bank slide and recreating it - that allowed me to publish successfully and everything seemed to work normally. Can you take a look at the attached copy and let me know how that behaves for you? 

Ashley Terwilliger

Hi Simon,

Glad that one is working for you. I had to do the import, and then recreate the bank. I would say it's something connected to an element of corruption in the file, and file corruption is unpredictable, and there's no straightforward way to determine what causes it. Common causes are environmental (disk errors, power outages, improper shutdowns), viruses, failed Windows updates, and even file size (i.e., very large files have a higher risk of corrupting).

Consider these preventative measures to protect your project files:
 
1) Save and publish projects on your local hard drive. Working on a network drive or external USB drive can cause erratic behavior.
 
2) Save incrementally. If your app has an AutoRecovery feature, take advantage of it. If not, save a new version of your project every hour or so with a new file name each time. If a file becomes corrupt, you'll still have a working version available.
 
3) Install Dropbox. Snapshots of changes in your local Dropbox folder are kept for 30 days. If a file is damaged or deleted, you can restore a previous snapshot: https://www.dropbox.com/help/11/en.
 
4) Don't leave the app open and unattended for long periods of time. Some users have reported file corruption after leaving their apps open overnight. It's possible that a malware scan or disk backup could run because the machine is idle, making your app vulnerable to crashing.
Ashley Terwilliger

Hi Chris,

Thanks for reaching out here and sharing the image - did you review the information previously shared in terms of working on local project files, importing into a new project, etc.? That worked previously for the file Simon shared - but you can also look to confirm that you're working on the latest update of Storyline 2, Update 7. 

Ashley Terwilliger

Hi Chris,

Within Simon's file I wasn't able to determine a specific cause, but corruption is unpredictable and notoriously tricky to track down. If you're following the guidelines shared above, those are good steps to prevent any corruption issues and if you'd like our team is always happy to take a look at a file to see if there is something we can track down. You can connect with our Support engineers here and they're available 24/7.