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, we're two years on and we're still seeing freshly published courses committing every 10 minutes instead of every 1 minute despite FORCED_COMMIT_TIME = "60000";.
We've shed a bit more night on it though:
- Running a course in Google Chrome shows an auto- ommit every 1 minute
- Running a course in IE11 shows an auto- ommit every 10 minutes
We've tried two different courses and it's the same.
So why is IE11 different to (say) Chrome? Well IE11 is running the course in "Flash" whereas Chrome is running it in native HTML5.
So we've disabled Flash in IE11 to run the Native HTML5 and we then got the correct 1 minute auto-commit.
So this might be a bug in the Flash framework. Are you seeing the same situation? Thanks.