8 min read

Canvas Quiz Log Shows Answers at Once? What It Means

A burst of answers at one timestamp usually means one Canvas autosave carried them all. What causes it, what looks suspicious, and what the log shows.

⚡

ExamClutch reads each question on the Canvas quiz page and fills in the answer with a double-click, so the quiz page never loses focus. It works on unproctored quizzes in ordinary Chrome, not under LockDown Browser or proctoring.

Usually, one save carried all of those answers at the same moment. In Classic Quizzes, Canvas logs an answer when the page's autosave reaches its server, not when the student clicks or types, and one save can hold many questions. A burst is a timing artifact until the answer history says otherwise.

How Canvas actually records an answer

Instructors on r/canvas keep posting logs where a student "answered questions 4–20 in 3 seconds." Instructure's help pages don't explain how that happens, so we read the Classic Quizzes code in Canvas's public source (the canvas-lms repository on GitHub). Here is how it works:

  • The quiz page saves the whole form, not one answer. Each save sends every answer on the page to Canvas.
  • A save happens when: you click a radio button or checkbox with the mouse; a text box or dropdown registers a change (normally when you click out of it); you flag a question; you return to the quiz tab; you upload a file; or you leave the page. A timer also saves every 30 seconds.
  • Canvas turns each save into at most one log entry. It compares the save with the answers it has already logged and drops anything unchanged. Everything new goes into a single entry. When there is more than one question, the log labels it "Answered the following questions:" and lists them all.
  • The timestamp is when the save arrived. The log shows elapsed time since the attempt started (30:25), measured on Canvas's server.

So "answered 17 questions in 3 seconds" really means "between one and a few saves, landing within 3 seconds, carried 17 new or changed answers." The log cannot show when each answer was actually picked or typed.

Other entries are batched as well. "Viewed," "Stopped viewing" and "Resumed" are queued in the browser and sent every 15 seconds, and the log shows when they arrived, not when they happened. Treat any single timestamp as approximate.

All of this describes Classic Quizzes. New Quizzes keeps its own log, and how it groups answers isn't published.

The innocent causes of a burst

Cause What the log shows How likely / how sure
Several answers changed between two saves One "Answered the following questions" entry Confirmed in Canvas's code
Answers picked with the keyboard Answers wait for the 30-second timer, then land together Confirmed in code (keyboard picks skip the instant save)
Internet dropped, then came back Nothing for a while, then one entry with everything Confirmed in code: failed saves retry every 30 seconds
Fill-in-multiple-blanks, matching, multiple answers, multiple dropdowns Answered at the very start of the quiz Documented by Instructure as an autosave quirk
Essays written in another app, pasted in quickly Full essays appear in a short run of entries Likely; matches how saving works
Rich content editor timing on essays Essay text reaching a save later than it was typed Plausible, not documented, not tested by us
All questions on one page vs. one at a time Bursts are easier on one page Likely, inferred from code
A second open copy of the quiz Answers re-logged when the other copy saves Possible, unverified

Saved together. Answer five multiple-choice questions with the keyboard in 25 seconds and the next timer save logs all five at once. Saves also skip if one is already running or the last one was under a second ago, so fast changes get folded into the next save.

Internet drops. When a save fails, Canvas shows a "Connection to … was lost" warning and retries every 30 seconds. Everything answered offline arrives in the first save that gets through.

Essays typed elsewhere. Many students draft long answers in Google Docs or Word so they don't lose their work. Pasting several essays in quick succession produces entries seconds apart, sometimes merged.

The rich content editor. Essay boxes use Canvas's rich content editor rather than a plain text box. Canvas doesn't document when text typed in that editor makes it into a save, and we haven't tested it. If it syncs only at certain moments, several essays could arrive together. That's a hypothesis.

One question at a time. With every question on one page, many answers can sit there until a single save picks them up. With one question per page, moving between questions tends to save as you go, so a big same-second burst is less natural there. This comes from reading the code, not from testing.

Restored sessions. Canvas doesn't re-log answers it already has, so simply resuming a quiz shouldn't create a burst. A second tab or device saving its own copy of the page might, but we couldn't confirm that.

What doesn't look innocent

The timestamps prove nothing either way. What instructors check next is what decides a case:

  • The answer history. Click a question in the log and Canvas shows every saved version of the answer. An essay that grew across several saves was typed in Canvas. An essay that appears fully formed in its first and only save was written somewhere else.
  • Time away right before the burst. Coming back to the tab triggers a save, so an answer entry right after "Resumed" is normal. A five-minute "Stopped viewing" gap followed by seventeen finished essays is what draws attention. See the stopped viewing flag explained.
  • Total time against the work. Seventeen thoughtful essays in a 30-minute attempt don't add up, however the saves were batched.
  • Identical text. Matching wording across students, or prose in a style the student doesn't use elsewhere, counts for more than any timestamp.
  • A shared pattern. Several students bursting at the same moment points to a Canvas or network problem.

For students: what the log shows about your time

Can your teacher see how many minutes you spent on each question? Not directly. There is no per-question timer. The log shows when each question first scrolled into view and when each save carrying your answer arrived. An instructor can subtract one from the other, but because saves are batched, the result is rough. Your total time on the attempt shows up plainly.

Are the times you picked answers logged? Sort of. Each answer is stamped with the time the save carrying it reached Canvas. That is usually within about 30 seconds of when you chose it, and much later if your connection dropped. The log also keeps every changed answer, not just your final one.

If your own log shows a burst, the honest explanation is usually the right one: you drafted elsewhere, your Wi-Fi dropped, or you used the keyboard. For the rest of what the log records, see Canvas quiz logs explained and whether Canvas can see copy and paste. Tab switches are their own entries. That's why in-page tools such as ExamClutch, which never leave the quiz tab, don't produce them.

For instructors: reading a burst fairly

  1. Check the quiz type. Only the Classic behavior above is confirmed.
  2. Rule out the documented quirk. Fill-in-multiple-blanks, matching, multiple-answer and multiple-dropdown questions can show as answered at the start purely from autosave.
  3. Open the answer history for the burst questions. Earlier partial versions mean the burst is a save artifact.
  4. Look at the minutes before the burst for "Stopped viewing" gaps or a long silence that fits a dropped connection.
  5. Ask the student how they worked. "I wrote it in Word first" is common and checkable in the document's version history.
  6. Weigh the content, not the clock. Instructure itself says the log isn't meant to validate academic integrity. Logs are also kept only six months, so act within that window.

For the rest of the screen, see the professor's view of the quiz log. For students logged as leaving when they didn't, see this guide.

Answer inside the quiz with ExamClutch

ExamClutch is a Chrome extension that reads each question on the Canvas quiz page and fills in the answer when you double-click it. Answers go into the real inputs on the page, so nothing is typed in another window and no tab switches show up in the log. It also works on Blackboard, Brightspace, Moodle, Schoology, McGraw Hill and Google Forms.

The honest limit: it works on unproctored quizzes in ordinary Chrome. It doesn't run under LockDown Browser or proctoring software.

FAQ

Why does my Canvas quiz log say I answered several questions at the same time? One autosave carried all of them. Each save becomes one entry listing every answer that changed since the last one.

Does a burst of answers in the quiz log mean cheating? No. It means the answers reached Canvas's server together. Instructors decide by looking at the answer history, time spent away from the page, total time and the content itself.

Can Canvas see how long I spent on each question? Not as a number. The log shows when questions came into view and when answers were saved, which gives a rough estimate. Your total time is shown directly.

Are answer times logged in Canvas quizzes? Yes, but each answer is stamped with the time its save arrived, not the moment you clicked. Changed answers are logged too, not just your final ones.

Why did essay questions all show as answered at once? Most likely the text was on the page before a single save picked it up. Common reasons are pasting drafts from another app, a dropped connection, or how the essay editor syncs. The essay's saved versions show which it was.

Is the New Quizzes log the same? No. New Quizzes uses its own log on the Moderate page. It also autosaves, but Instructure doesn't document how it groups answers, so the Classic behavior here may not carry over.

Ready to stop fighting your LMS?