Forum Discussion

kperk7692's avatar
kperk7692
Community Member
22 days ago

Corrupted triggers?

I've spent about 2-2.5 weeks working on this Storyline course. It's all storyboarded out, literally everything is good to go. We were out for snow recently so I spent DAYS working on this. Then, al...
advice
storyline 360
brianmcaudill's avatar
brianmcaudill
Community Member
21 days ago

I created an AI agent that knows the .story schema and so it can read and diagnose issues and fix them. Here is what it says about what happened. Contact me directly if this seems like what may have happened. 

Root Cause: Corrupted copiedG References in Trigger Definitions

 

The .story file has corrupted trigger-to-object associations throughout every slide. The copiedG attribute in triggers

(which tells Storyline which object owns the trigger) points to the wrong objects.

 

Evidence from slide5.xml (Question 1):

┌───────┬────────┬─────────────┬──────┬─────┐

│ Button # │ Button GUID │ Trigger's copiedG │ Points To │ Status │

├──────┼─────────┼─────────────┼──────┼─────┤

│ 1 │ 4506f0ca... │ 4506f0ca... │ Same button │ ✓ OK │

├─┼── ──────┼─────────┼─────────┼─────┤

│ 2 │ 978c5bda... │ 26fd53cd... │ Button #7 │ CORRUPT │

├─┼─────────┼────────┼───────┼────────┤

│ 8 │ 4b89ae13... │ 80c1a12b... │ Button #13 │ CORRUPT │

├─┼─────────┼────────┼────────┼───────┤

│ 14 │ 0231e07c... │ 966171b4... │ The SLIDE itself! │ CORRUPT │

└──┴────────┴────────┴────────────┴───────┘

What This Means

 

When the user clicks on Button 2 to edit its trigger:

1. Storyline reads the trigger's copiedG attribute

2. It finds 26fd53cd... (Button #7's ID)

3. It jumps to select Button #7 instead of Button #2

4. The user ends up editing Button #7's trigger, not Button #2's

 

Scope of Corruption

 

All 10 slides are affected with similar mismatches:

- slide.xml - 3 mismatches

- slide2.xml - 3 mismatches

- slide3.xml - 2 mismatches

- slide4.xml - 2 mismatches

- slide5.xml - 6 mismatches

- slide6.xml - 2 mismatches

- slide7.xml - 2 mismatches

- slide8.xml - 2 mismatches

- slide9.xml - 3 mismatches

- slidea.xml - 3 mismatches

 

Likely Causes

 

1. Copy/paste corruption - Copying objects with triggers may have failed to update the copiedG references

2. Storyline bug - A save operation or undo/redo cycle corrupted the GUID references

3. File format version mismatch - Opening in a different Storyline version may have introduced the corruption

brian@actyra.com