Forum Discussion
3rd Party Cookies affecting Storyline completion
It is my understanding that browsers accessing a Storyline 360 product in an LMS, need to allow the use of 3rd Party Cookies to ensure the presentation functions correctly. (Particularly for the tra...
Hi Frank, 5-10% is a very high number and does suggest an issue on the LMS or user end. After you have confirmed the content tracks accurately and consistently on SCORM Cloud, it would be worth exploring network issues.
Regarding auto-commit, yes this could definitely help as the LMSCommit("") method is not issued after each data transaction from the Storyline content.
I'm not sure how frequently Storyline issues LMSCommit(""), but in a small experiment I just did, LMSCommit("") was only issued when I closed the content. This could be risky where there is network instability as there is only one chance for the data to be committed to the database. If set to auto-commit, it will increase writes to the database, and slow the response times down, but will make the data persistence more stable.
