Hi Richard,
We tried adding the debug in #1, but cannot move the student to the latest question version through any method, and we're not allowed to regrade the entire exam on our live system. And as stated, we're unable to replicate this issue in our testing servers. Curiously, all three CodeRunner questions in the exam don't move to the latest version (usually methods are to go to Quiz Settings and press 'Save', or regrade the students' attempt). I had a brief chat with Tim Hunt about this, and he's not sure why that has happened either.
For #2 No, sorry. Next time we upgrade (for our December release in late November), I can try running the regrade and see if anything changes.
#3 I don't have sight of those, but my developers have said they can't see anything obvious.
#4 Unfortunately our environments are heavily locked down and we can't mix and match the live and test servers/sub-servers :-(
I think we've probably spent as much time troubleshooting this as we can our side, but at least this problem is documented for the future in case anyone else has a student response get stuck in the same sort of state. Hopefully #2 will shed some more light on it after our next upgrade hits the live environment.
We tried adding the debug in #1, but cannot move the student to the latest question version through any method, and we're not allowed to regrade the entire exam on our live system. And as stated, we're unable to replicate this issue in our testing servers. Curiously, all three CodeRunner questions in the exam don't move to the latest version (usually methods are to go to Quiz Settings and press 'Save', or regrade the students' attempt). I had a brief chat with Tim Hunt about this, and he's not sure why that has happened either.
For #2 No, sorry. Next time we upgrade (for our December release in late November), I can try running the regrade and see if anything changes.
#3 I don't have sight of those, but my developers have said they can't see anything obvious.
#4 Unfortunately our environments are heavily locked down and we can't mix and match the live and test servers/sub-servers :-(
I think we've probably spent as much time troubleshooting this as we can our side, but at least this problem is documented for the future in case anyone else has a student response get stuck in the same sort of state. Hopefully #2 will shed some more light on it after our next upgrade hits the live environment.