fixed the links in the post above.
I'm pretty sure scorm debug mask accepts commas to allow multiple users to be set but it's been a while since I've used that setting so you might need to test it out and see.
it can be hard to diagnose issues with SCORM - it's even worse if you can't reproduce the conditions. JavaScript can be really fragile.
Good luck!
Thanks for the links.
Yep ... very difficult to diagnose if one cannot reproduce ... backed up one course that had one of those SCORM's in it, restored to another server ... OS and versions of everything very close. Did that cause the live logs on a node scroll so fast one can't really see anything!!! And even tail -f on logs with a grep for IP address and anything that had 'scorm' in the URL didn't lead to any clue ... might have picked an ip and user behind that ip wasn't having any issues.
Course over there had no issues - but wasn't a node in an LB system either.
Will continue to dig however.
'spirit of sharing', Ken
Follow Up to own posting ... how sick is that!!!
Thought I'd share what have learned so far ... and a method to test the SCORM with debugging on ... NOT in the LMS (however).
Specifics may apply so:
The SCORM am investigating ....
Created using Storyline 360
version: 3.16.15842.0
ADL SCORM 1.2
Community discussion about a bug related to autocomit
https://community.articulate.com/discussions/articulate-storyline/forced_commit_time-value-of-60000-60k
A page tha describes using SCORM cloud.
https://community.articulate.com/articles/how-to-troubleshoot-your-lms-with-scorm-cloud
Note it does say that the URL method ... ie, linking that in the Moodle,
will not share the data back to the Moodle. But, is that important?
Just interested in passing score to be able to move on.
****
Debugging
https://community.articulate.com/articles/the-secret-to-lms-debugging
'spirit of sharing', Ken