Forum Discussion
How can I add an LMS.Commit/Commit Event when a custom LMS doesn't bookmark with suspend_data call
Hi Kristen!
Are you noticing this problem is happening in Chrome and Edge?
If so, we've also seen that courses exited by closing the browser window in Chrome 83 or Edge are not showing as complete or resuming as expected.
Here are some details on the Chrome 83/Edge behavior:
Chrome has deprecated a technology that was used by many LMSs to allow a course to communicate back to the LMS when the course window is closed (as opposed to using the Exit Course button).
If your LMS hasn't upgraded their system, or if you're using an older version of your LMS that doesn't include an update to address this change, the course cannot communicate progress or completion properly. This causes learners to start over from the beginning instead of resuming a course or recording completion after they close the browser window.
Please reach out to your LMS and find out if they have released an update to address the Chrome changes.
Is there a way to add explicitly LMSCommit/Commit in Rise like in StoryLine approach described in this thread https://community.articulate.com/discussions/articulate-storyline/manually-invoke-lmscommit-on-slide-load-with-js by Steve Flowers
"At any rate, if you really wanted to you could call LMSCommit(); on every slide load. No harm, I suppose. I wouldn't try to call it once ever second or anything like that. Too often and you're creating unnecessary requests. Doesn't sound like that's your goal.
JavaScript Trigger placed on your master slide when the timeline starts:
LMSCommit(); "