Hi Hannah - probably not quite enough info here for the Totara team to diagnose this - here's my understanding of the part that I think could be a bug with the way attempts are generated in Totara.

Something is incrementing the "attempt" var without an actual attempt occuring

something is registering an "empty" attempt in SCORM without the user actually entering and loading the SCORM correctly.

A possible location for this in the totara code (I haven't looked at the totara code to trace this so I might be wrong) could be the way pop-up windows are handled/blocked.

Eg - user loads SCORM but pop-ups are blocked, Totara registers this as an "attempt"
when user reloads with pop-up blocked instead of using the previously created "empty" attempt it generates a new one.

For the Totara team to resolve this may need a copy of the SCORM you are using - I guess one of them will get in touch for further info if required.

Note to Totara LMS team - feel free to ping me on jabber/irc if you want more info - thanks!

Hi Hannah,

I looked into it - it seems to be a problem with the way Internet Explorer handles form submission when the popup blocker gets activated - the user gets prompted to resubmit the form and if they do it creates the false record.

I've written a workaround that seems to resolve the problem, we'll include it in this week's release (1.1.15) which is due out tomorrow.

I've sent Catalyst the patch in case you need it sooner.

Thanks,

Simon