Invigilation candidate logs

When a user* clicks on a candidate listed on the invigilator dashboard, this will open up the Candidate Logs for that candidate.

Example screenshot of the candidate logs page after clicking on a candidate:

The candidate logs shows the actions / progress of the candidate:

• Timestamp - time and date of the action
• Attempt - shows the attempt number for the candidate - use the dropdown to see different attempt numbers if applicable.
• Action - list the action by the candidate - see below.
• Question number - this is the position of the question in the overall attempt.
• Item ID - lists the question ID as given by the author in the Collection / Library.
• Error - lists any front-end error
• IP address - lists the IP address logged at the time.

Actions listed in the candidate logs:

A typical exam would register the following actions for a candidate

1. Page visited - candidate visited welcome page
2. Exam started - The candidate has clicked start assessment
3. Question visited - candidate opens the first question
4. Question answered - client side message (front-end) that candidate answered
5. Candidate save answer - server side message (back-end) that an answer was received and saved. 
6. Repeat of question visited, question answered and candidate save answer messages. For some questions like Essay questions a client side message may appear multiple times if the candidate changes his answer before the candidate save answer message.
7. Exam completed - candidate handed in (this means the candidate clicked the 'Complete Assessment' button and subsequently clicked the 'Confirmed' and after that the 'Finish' buttons to hand in his work.
8. Page visited - this means the finish page.

Actions:

• Page visited - candidate visited welcome page
• Exam started - The candidate has clicked start assessment
• Question visited - candidate opens the first question
• Question answered - client side message (front-end) that candidate answered
• Candidate save answer - server side message (back-end) that an answer was received and saved. 
• Repeat of question visited, question answered and candidate save answer messages. For some questions like Essay questions a client side message may appear multiple times if the candidate changes his answer before the candidate save answer message.
• Exam completed - candidate handed in (this means the candidate clicked the 'Complete Assessment' button and subsequently clicked the 'Confirmed' and after that the 'Finish' buttons to hand in his work.
• Page visited - this means the finish page.
• Exam opened - Exam is opened and able to start (in case of a timer, this will start counting)
• Message from invigilator viewed - A message was sent during the exam and the candidate viewed the message
• Exam status changed (server log)
  • Internet loss
  • pause/start of the exam (action done by invigilator)
  • extra time was added by invigilator
  • Exam was voided
• Uncaught exam error - Unknown error, this doesn't mean it had an affect on the candidate exam, but something happend which Cirrus wasn't able to define in the logs. 
• Unload page
  • reloading browser tab
  • Exiting browser tab
• Last answer Id is not valid - questions were sent to the server in the wrong order, does not have impact on the candidate
• Before page unload - moment before reloading browser tab
• Caught exam error - There was an error which will be described, for example: Network Error
• Caught exam error with description starting with 'Queue error'

  Errors starting with "Queue error <queue id> and will retry, caught: " are NOT needed to report to Cirrus. These errors will not cause any issues, but are used internally to monitor.
  
  
• Question answer was not saved - somehow the answer wasn't able to save. This could be related to internet issues, however Cirrus will try to save the answer every few seconds.
• Connection lost - Candidate lost connection, possible internet connection problems (only appears when using the 'heartbeat' functionality)
• Connection restored - Candidate restored internet connection (only appears when using the 'heartbeat' functionality)
• Answers queue stuck - Answer stays in the queue for some time (60 seconds) or there are more than 50 unsaved answers in the queue. It might be caused by disconnect, slow connection, issues on the webserver. Does not affect the exam of the candidate.
• Proctorio status active - every 5 minutes the system will check if there is still a connection with proctorio
• PROCTORIO_STATUS_ERROR - Proctorio lost internet connection. The candidate will be forced to re-enter the exam to continue in order to establish a new connection with Proctorio