Forum Discussion
FORCED_COMMIT_TIME value of 60000 (60k)
When publishing a Storyline 2 course for LMS, the configuration.js file has a setting " FORCED_COMMIT_TIME " which is set to "60000". Am I safe to assume that this is the number of millisecon...
Hi Chris,
I know this discussion has gone on for some time, but I wanted to confirm what version of Storyline you're using? We had an issue in Storyline 360 where the HTML5 LMS output sends a status to the LMS even if we set var FORCED_COMMIT_TIME = from 60000 to 0. That was fixed in Update 16, and it'll be fixed in the next update of Storyline 3 as well.
If you are still seeing something odd in your files, could you connect with our Support team so that we can take a look!