Yeah, my first thought was "We could just add a new setting under auto submit for whether or not to auto submit empty assessments" but really we don't want to do this. It should just be something predictable and documented as you're saying. And the most predictable thing is that any assessment in any state of progress be submitted which is the current behavior in 11.

Putting more informational text in the UI about what auto-submit will do if enabled (for an instructor) and possibly what would happen as a student if auto-submit is enabled would be the only additional work I'd do here. I can create a new issue for this.

Matt, agreed.  As with so many T&Q related things, it is tricky and is perhaps impossible to find consensus on what "makes sense".  That is why there are so many settings in Samigo in general.  (And I do not_ think we need _another one to address this.)  I think the better part of valor here is to pick a predictable and consistent behavior and document it clearly.  In this case, that means *all attempts are auto-submitted,* even "accidental" ones, period.  I added my previous comment to clarify for anyone else who drops by here that there is no special logic to excuse empty submissions.

I'm going to approach this by attempting to train our instructors in the use of the 'delete submission' functionality in Samigo.  If they encounter an "empty" submission that they determine should be tossed out they can delete it themselves.  (It might be nice if there was a UI way to un-delete those, though, in case of mistakes.)

Yeah John, I'm not sure the solution here. We have faculty that want every "attempt" submitted, but is really an attempt if they didn't answer anything? And with the default "highest score" submitting even an empty attempt isn't really a problem, it's just those other scoring options.

I think back last May this is kind of what we were talking about, but seeing if questions were attempted (rather than just wrong) would also require some additional work.

We could put more information in the UI to both students and faculty about what would happen if they starting a new submission as while using the "last score" and "average score" options with multiple submissions, but probably it's better just to figure out a better way to handle it.

There's some statements in the comments here that can be easily misinterpreted–or at least I misinterpreted them–so I'm going to clarify for anyone else who finds themselves here.

I just verified this in the nightly 11 and 12 servers.  Here is what happens in a quiz set up for multiple attempts: 

1. student opens the quiz,

2. answers questions,

3. submits it 

4. student clicks the quiz again but does not answer any questions, leaves page without saving, exiting, etc.

Result: That 2nd "empty" attempt will be submitted by the auto-submit job, in both Sakai 11 and 12. 

If the quiz settings are set for "Highest Score" then it will not overwrite the previous attempt. (Zero can never be greater than zero.)  If the settings for the quiz are "Last Score" then the student will have 0 points for the quiz.  If the settings are for "Average Score" then it will average in a 0-point attempt into their final score.

So, per Karen's comment above, if a student clicks on that active link and then says "whoops" and closes it (I see this relatively a lot), they will be penalized for that mistake if the quiz uses "Last score" or "Average score".  This makes our faculty who use "Last Score" think that the auto-submit feature is "broken".  

Verified on 12x that a second submission was not autosubmitted after the autosubmit job processed.