SCORM : When Scorm 2004 is exiting, ScormDriver commit function gets called many times

[garyc56322630]

Hello,

After publishing to Scorm 2004 with any template, I noticed that the commit function is getting calls many times when terminating a SCORM.

It is really an issue as our LMS captures 3 times the same information. 

Has anybody experienced this behavior?

[RodWard]

Could be an issue with your LMS.

Try uploading your SCORM to SCORM Cloud online LMS and check the logs there to see how many times it commits.

[garyc56322630]

Hi,

Thanks for the advice. 

I did this and still have many commits. (see DebugLog)

The "Calling Commit" statement is repeated many times as I send only one unique Terminate... It very strange

Thanks ,

DebugLogs - Copy

Gary

[TLCMediaDesign]

More than likely the commit command is issued every time another command is issued. So it may be writing the cmi.location, cmi.suspend_data, an others and the commit is issued after these calls as well.

[garyc56322630]

Thanks for your answer. 

Is there anything I can do to prevent this and this hardcoded in the scormdriver.js? Should I live with this behavior?

Is this something usual and I should write my LMS API accordingly?

For instance I need to  accumulate the cmi.total_time from the cmi. session_time?

All my interactions are written many times in LMS. Should I check for existing interactions before rinting in theDB?

Thanks for your help!

[RodWard]

I don't think this behaviour should be seen as an issue.  Captivate uses SCORM drivers supplied by Rustici Software.  This company supplies SCORM software to more than 50 of the biggest LMS vendors around.  They are recognised experts in the field.  If they have written the drivers to perform the calls this way then there is probably a very good reason for it.  I would not mess with it.