Quiz didn’t save

If a quiz looks broken after editing, work through these causes.

Symptom 1: “Quiz is empty after I clicked Save”

You’d written questions, clicked Save as Draft, and the quiz now shows zero questions.

Cause

A bug in the early Save-as-Draft flow could delete existing questions before insertions completed if the insert failed silently. This was fixed in May 2026 (Phase 13).

If you’re seeing this after May 2026, it’s a different bug. Report it.

What to do

Don’t panic. Quiz questions ARE recoverable via the audit log — every question creation is recorded.
Email support@getwisteria.com with the module ID. We can reconstruct from audit data.
In the meantime, don’t keep clicking Save — that might overwrite the recoverable state.

Symptom 2: “Save as Draft” button doesn’t seem to do anything

Clicking the button shows no spinner, no toast, no visible effect.

Possible causes

Network issue. Open browser dev tools → Network tab → look for the save POST. If it failed, the issue is network.
A validation error you can’t see. A required field is missing (e.g. an MCQ question with no correct option selected).
JavaScript error in the page. Open dev tools → Console — look for red errors.

What to do

Refresh the page. Re-enter the changes. Try Save again.
If a validation error is the issue, the form usually shows red inline indicators near the offending field.
If JS is broken, sign out, sign in, retry. If the page is consistently broken, file a bug.

Symptom 3: Save succeeds but the Ready to Submit button doesn’t enable

After saving, you can’t mark the module Ready.

Likely causes

Quiz has zero questions. Ready requires at least one question.
Question is incomplete. Each question needs a complete state — MCQ needs at least 2 options + a correct answer; Fill in blank needs a correct answer text; Matching needs at least 2 pairs; Oral needs a model answer + at least 3 keywords.
Flashcards are stale. If cards_updated_at is older than quiz_generated_at, Ready stays disabled. This means: you generated the quiz, then edited cards, but the system thinks cards need updating relative to the latest quiz.

What to do

For the first two: complete the question.
For the stale flashcards case: edit any card and re-save. The cards_updated_at updates; Ready unlocks.

Symptom 4: AI quiz generation seems to fail

You clicked Generate quiz with AI and nothing seemed to happen, or the result was empty/broken.

Possible causes

The module has no flashcards. AI quiz generation reads from the deck — no cards means nothing to generate from.
The flashcards are very short or very few. Claude needs material to work from; fewer than 3 cards usually produces weak results.
A transient AI provider issue. Anthropic occasionally has slowdowns.
A specific question generation error — the AI produced a question that violated a column constraint (e.g. missing correct_answer for an MCQ).

What to do

Ensure the module has at least 5 reasonable flashcards before generating.
Try again — generation is non-deterministic; a second attempt often succeeds.
If repeated failures, simplify the existing flashcards (super-long ones can confuse the model). Try generating just a few questions at a time.

Symptom 5: A specific question won’t save (others save fine)

Single question is rejected, others are fine.

Likely causes

Question type has invalid data. E.g. a Matching question with one pair (needs minimum 2), or an Oral question with zero keywords.
The correct_answer column has a problem. Historically, certain question types accidentally tried to set this when they shouldn’t (Matching, Oral — both leave it null).

What to do

Open the question, double-check every required field.
For Matching: ensure 2+ pairs.
For Oral: ensure model answer + at least 3 keywords + pass threshold (50–95).
Save just that question with manually-entered minimums; if it now saves, the original data had something off.

Symptom 6: Quiz works for trainer but fails for learner

The trainer can preview the quiz; the learner sees a broken quiz.

Possible causes

The quiz contains a question type the learner version doesn’t render — unlikely, but possible after a Wisteria update.
The module isn’t actually published. Trainer preview works on drafts; learners need published.
The learner’s browser is outdated.

What to do

Confirm the module is published and assigned.
Have the learner refresh (Cmd+Shift+R / Ctrl+Shift+R for hard refresh).
Test as the learner yourself — use the “View as learner” button if available, or sign in to a learner test account.
If the issue persists, file a bug with the learner’s browser/OS info.

Symptom 7: AI Match Quiz proposed cards but they don’t insert

You clicked Add selected; the panel closed but no new cards appeared in the deck.

Possible causes

Network issue during insertion. Some cards may have been saved; others not.
The cards_updated_at wasn’t bumped — historically a bug; if you see this after May 2026, report it.

What to do

Refresh the page. Check if the cards are actually there (sometimes the UI doesn’t update but the DB did).
If still missing, retry the AI Match flow.
If repeatedly broken, file a bug.

General advice

Always work in small increments. Save often.
Don’t keep many tabs open of the same module — they can race on saves.
If something looks lost, check the audit log first (super_admin). Every change creates a recoverable record.
Sign out and back in to clear stale client state if behaviour is unexplained.

When to file a bug

If you’ve tried the above and the quiz is still broken, file a bug at support@getwisteria.com with:

Module ID (in the URL)
Description of what you did and what happened
Browser + OS
Screenshot of any error or weird state
Audit log entries from the affected timeframe (super_admin can grab these)

We treat data-loss bugs as the highest priority and respond fast.