LearnDash Quiz Retake Not Working? 4 Real Fixes That Actually Work

A student clicks retake, gets the exact same quiz, and ends up stuck at the same score. If you’re dealing with a LearnDash quiz retake not working, the button is usually greyed out, missing entirely, or clickable but the attempt never actually resets, and none of the obvious troubleshooting (clearing the browser cache, checking the student’s account) tends to fix it. The real cause almost always sits in one of a handful of quiz settings most course creators never open after the initial setup.

This guide walks through every real cause, in the order they actually show up in practice, so you can identify your specific case instead of guessing your way through generic advice.

How LearnDash Handles Quiz Retakes in the First Place

Every LearnDash quiz has its own Restrictions tab, separate from the lesson it’s attached to, and that tab is where retake behavior actually lives. A handful of settings there work together: how many times a student can attempt the quiz, whether there’s a required gap between attempts, and whether the quiz needs a prerequisite satisfied before it will open again. None of these settings are visible to the student. They just see a locked button or a quiz that looks identical to their last attempt, with no explanation of why.

That’s the core problem course creators run into: LearnDash doesn’t surface the blocking condition anywhere in the student-facing UI. It’s enforced silently on the backend, which means a perfectly working retake system can look completely broken from the student’s side.

It also means the fix is rarely a matter of reinstalling a plugin or contacting hosting support. In the overwhelming majority of real cases, every setting involved is sitting right there in the WordPress admin, already correctly saved, just configured in a way that doesn’t match what the course creator actually intended. Working through the causes below in order is almost always faster than opening a support ticket with LearnDash directly, since most support responses for this exact issue point back to the same handful of Restrictions-tab settings covered here.

Common Scenarios Where a LearnDash Quiz Retake Won’t Work

Before the full breakdown, here are three patterns that show up constantly in course-builder support threads. See if one matches what you’re seeing:

1. The Repeats Setting Is Set Too Low

Under a quiz’s Restrictions tab, the Repeats field controls how many total attempts a student gets. Left at its default, it’s usually unlimited, but during course setup it’s common to set a specific cap, and easy to set it lower than intended, or to accidentally leave it at a testing value like 1. Once a student uses up their allotted attempts, the retake option disappears completely, with no message explaining that the cap has been reached.

This is the single most common cause reported for a LearnDash quiz retake not working, precisely because the setting is easy to configure once and forget about. Per LearnDash’s own quiz access and progression documentation, retake limits and access controls are set on a quiz-by-quiz basis, not globally, which is exactly why one quiz can behave differently from another in the same course.

2. A Wait Period Is Still Counting Down

LearnDash supports a required gap between quiz attempts, meant to discourage students from immediately re-guessing their way to a passing score. If this Wait Period is set, and a student retakes too soon, they’ll see a locked retake option with a message about needing to wait, though the exact wording varies by theme and can be easy to miss on a smaller screen.

This setting is genuinely useful for high-stakes assessments, but on a low-stakes practice quiz it can feel like a bug rather than a deliberate pacing decision.

3. The Question Pool Is Too Small

If a quiz draws a random subset of questions from a small bank, a retake can pull the exact same questions in the exact same order, making it look like nothing changed even though the retake mechanism itself worked correctly. Students often report this as “the retake isn’t working” when the real issue is a lack of question variety, not a broken retry system.

This becomes more noticeable the smaller the gap is between the pool size and the number of questions shown per attempt. A ten-question pool showing all ten questions every time will always feel identical on retake, regardless of shuffle settings.

4. A Prerequisite Is Blocking the Retake

Some courses configure a quiz to require completion of a specific lesson, or another quiz, before it can be attempted again. This is common in courses structured to force review of the material between attempts. If that prerequisite condition isn’t met, the retake option can appear locked or missing, and the reason is easy to miss since it lives in a different lesson’s settings entirely, not the quiz itself.

Other Reasons a LearnDash Quiz Retake Won’t Work: Plugin Conflicts and Caching

If none of the four causes above apply, two more things are worth checking before assuming it’s a deeper bug. First, test in an incognito or private browser window: a caching plugin can serve a stale quiz-results page to a returning student even after LearnDash has correctly reset their attempt server-side. Second, temporarily deactivate other plugins one at a time to check for a conflict, since LearnDash’s quiz-attempt data lives in user-meta, and another plugin writing to that same data (a gamification plugin, a custom reporting dashboard) can interfere with it.

If your site runs a caching layer like LiteSpeed Cache or WP Rocket, specifically confirm logged-in user pages are excluded from caching. Quiz and course pages should never be served from cache for a logged-in student, since attempt state is unique per user, and this is a surprisingly common cause on managed hosting where aggressive caching is enabled site-wide by default.

How to Check What LearnDash Actually Recorded

If you want to confirm the problem from the admin side rather than guessing, LearnDash’s own reporting gives you the real, per-student record. Go to LearnDash → Users, select the student in question, and open their course report. It shows every quiz attempt, the score recorded for each one, and the pass or fail state, which tells you definitively whether the system is actually blocking a genuine retake or whether the front-end display is simply out of sync with what’s recorded server-side.

Cross-referencing this report against the four causes above turns guesswork into a quick diagnosis: if the report shows only one attempt recorded but the student insists they’ve tried multiple times, you’re likely looking at a caching issue, not a settings issue.

A Quick Diagnostic Order to Follow

When a student reports a stuck retake, check these in order. It’s faster than guessing:

1. Open the quiz’s Restrictions tab and check the Repeats setting.
2. Check whether a Wait Period is configured and still active.
3. Check the question pool size relative to questions shown per attempt.
4. Confirm any prerequisite lesson or quiz has actually been met.
5. Check LearnDash → Users for the student’s real recorded attempts.
6. Test in an incognito window to rule out caching.

Checking Retake Issues Across an Entire Cohort, Not Just One Student

A single stuck student is usually a quick fix, but if a whole cohort reports the same problem at once, checking each account individually wastes time you don’t have. LearnDash’s Users report can be filtered by course, which lets you scan every enrolled student’s quiz attempts in one place rather than opening profiles one at a time. If the pattern is consistent across most students in a cohort, that’s a strong signal the cause is a site-wide setting (Repeats, Wait Period, or a prerequisite applied course-wide) rather than anything specific to one account.

The opposite pattern matters too. If only a handful of students in an otherwise unaffected cohort are stuck, that points toward something account-specific: a role or membership plugin restricting access differently for that subset, or those particular students genuinely not having met a prerequisite the rest of the cohort completed. Separating “everyone is stuck” from “a few people are stuck” early on saves a lot of wasted troubleshooting time, since the two situations have almost entirely different root causes.

A Note on Quiz Retakes and Certificates

If a course issues a certificate on quiz completion, a blocked retake has a second-order effect worth checking for separately: a student who can’t retake a failed quiz also can’t reach the passing score a certificate requires, which then shows up as a completely different-looking support request about a missing certificate rather than a quiz problem. If you’re troubleshooting a certificate complaint and the course includes a graded quiz, it’s worth working backward through the retake causes above before assuming the certificate configuration itself is at fault.

Why This Specific Problem Is So Common in LearnDash

A LearnDash quiz retake not working is such a widely reported issue because retake behavior is genuinely configurable in several independent ways at once: a repeat cap, a wait timer, a question pool, and a prerequisite condition. That flexibility exists because different course types need different retake rules. A certification exam legitimately needs a strict repeat limit and a cooldown period. A low-stakes practice quiz usually needs neither. The tradeoff is that every course accumulates its own specific combination of settings, and it becomes easy to add one restriction without remembering it interacts with another already in place.

This is also why generic troubleshooting advice, like clearing the cache or checking plugins, only resolves the problem some of the time. A retake blocked by a repeat cap needs a completely different fix than one blocked by a wait timer, even though both present identically to the student as a retake that simply won’t start.

There’s also a design tension worth naming directly: the same restrictions that prevent a student from gaming a quiz by repeatedly guessing are the ones most likely to get reported as broken. A course creator setting up assessments for the first time often copies restriction settings from a template or a tutorial without adjusting them for their own course’s stakes, so a low-pressure knowledge check ends up inheriting the same Repeats cap and Wait Period meant for a certification exam. Reviewing whether each quiz’s restrictions actually match its purpose, rather than leaving every quiz on the same defaults, prevents a large share of these reports before they happen.

Preventing This Before It Happens Again

The real fix isn’t just unblocking one stuck student. It’s auditing your quiz restrictions so this doesn’t keep generating support requests. Before launching a new course, or a new cohort of an existing one, walk through each quiz as a test student account and attempt a retake yourself. It takes only a few minutes per quiz and reliably catches this exact class of problem well before real students ever hit it.

Frequently Asked Questions

Can I manually reset a student’s quiz attempt?

Yes. From LearnDash → Users, you can open a student’s course report and clear a specific quiz attempt, which lets them retake it immediately regardless of the Wait Period or Repeats setting.

Does the retake count reset if I change the Repeats setting?

Raising the Repeats number after a student has already used their attempts gives them additional retakes going forward, but it does not erase their prior recorded attempts.

Is this fixable without a developer?

Yes, in most cases. All four causes above are settings changes inside LearnDash itself, not code fixes. If you’ve checked all four and it’s still not resolving, that’s when it’s worth bringing in someone to look at a possible plugin conflict.

Why does the retake show the same questions every time?

This is almost always the question pool being too small relative to how many questions display per attempt, not a bug in the retake mechanism itself. See cause 3 above.

Does this affect the whole course or just one quiz?

It depends on the cause. Repeats, Wait Period, and prerequisite settings are configured per quiz, so they typically affect just one quiz unless you’ve applied the same setting across the whole course. Caching and plugin-conflict causes tend to affect every quiz at once, which is a useful clue when narrowing down which category you’re dealing with.

Will upgrading LearnDash fix this automatically?

Rarely. Most cases of a LearnDash quiz retake not working are configuration issues, not bugs in LearnDash itself, so a version update won’t change a Repeats cap or an active Wait Period. It’s worth staying updated for security and compatibility, but don’t expect an update alone to resolve a stuck retake.