Resume on new course version problem

We absolutely need to be able to update our courses after they are released.

Our plan is to use scorm 2004 4:th edition as delivery format.

There seem to be built in functions for storing the state of objects and the value of variables.


Deleting an object with state, or a variable seems to shift the state of all objects created after the deleted one or all variables after the created one step - in the best scenario, in the worst scenario it crashes the player when loading the stored state.

Those two could of course be avoided bu never deleting things in updated versions of the course.


Adding variables seems not to work very well either, and not beeing able to add variables would be a worse problem...


Anyone having any suggestion?

9 Replies
Alyssa Gomez

Hi there John,

Can you help me understand a bit more about what's happening in your file? Let's start with these questions:

  • What version of Storyline are you using?
  • When you delete an object that has a state, what happens to other objects on the slide?
  • When you delete an object that has a variable trigger associated with it, what happens to other objects on the slide?
  • Could you record a short screen recording to demonstrate exactly what is happening?
Johan Bengtsson

Q1: Storyline 360 v3.12.14647.0

Q2 and Q4: See attached file.

Q3: I have not tested anything regarding triggers. I assume triggers are not stored in the resume data and therefore not an issue. Variables however show a similar issue, except that they can't be created without problems. I can of course make an example showing that too if needed.

Johan Bengtsson

I just realised that it is not creation order but Z-order that controls what order the objects are stored in the resume data. This is even worse than first exprected. Making an internal rule not allowing to delete an object is bad enough but could be handled. Not allowing to correct a bad Z-order is of course out of the question.

Ashley Terwilliger-Pollard

Hi Johan, 

I'd love to see this .story file you set up as well so that we can also play around with the exact example. I was having a difficult time following along in your PDF about deleting objects and seeing the state shift?

Also,  when you update (overwrite) existing course files in your LMS or web server, learners who previously started the course won't be able to resume where they left off. They'll start over at the first slide in the updated course. You'll want to keep this in consideration when updating courses that have already been delivered to learners. That could also explain the crash you're seeing. What LMS are you using? We do our testing in SCORM Cloud which would be a good baseline of how it's supposed to behave if you wanted to test there as well.