Forum Discussion

ChrisWalsh's avatar
ChrisWalsh
Community Member
10 years ago

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...
storyline 360
  • ChrisWalsh's avatar
    ChrisWalsh
    Community Member
    10 years ago

    Thanks Ashley,

    We've got our own LMS which is hosting SL2 courses.  We're getting occasional cases where users complete the course (got a printout of the certificate etc.) but we've not got a record on our LMS.  

    We've noticed that if there is a communication failure writing the SCORM data back via our API Adaptor, the exception is caught (in our adaptor) and logged but we're not alerting the user to the problem.  We're testing a fix for this (including a retry option).  

    However we're unsure about whether the heartbeat LMSCommit()s from SL2 are being fired or not and if they are whether they are doing so at the frequency given by FORCED_COMMIT_TIME.  Certainly they don't appear to be happening as frequently as 60000ms (=1 minute) - which is a value which we would be happy with BTW.

    Thanks,

    Chris