LLM course certificate

Beginners
4

Hmm… Since your case is about the Agents Course, I think it is close to, but not the same as, the LLM Course case. That said, there seem to be quite a few similar reports:

My practical read is:

If the learner has already completed the relevant Agents Course path, their final result is visible on the Unit 4 leaderboard, and the only failing step is the final certificate claim on the certificate page, then a course-side or app-side issue remains very plausible. I would not reduce this too quickly to a browser-local problem if the usual browser checks have already been tried.

The key reason is that the public Agents Course materials already define the process as a multi-stage flow, not one single atomic action.

The official Agents Course introduction says there are two different certificate paths:

  • a fundamentals certificate
  • a completion certificate

That same page says the completion certificate requires:

  • Unit 1
  • one use-case assignment
  • the final challenge

The official source page in the course repo says the same thing:

Separately, the official Unit 1 certificate page says the fundamentals certificate requires completion of Unit 1 and an 80 percent passing score on the final quiz.

For the completion path, the official Unit 4 introduction and Unit 4 hands-on page define the final challenge layer, while the official Claim Your Certificate page says that if the learner scored above 30 percent, they can:

  1. visit the certificate page
  2. sign in with their Hugging Face account
  3. enter their full name
  4. click Get My Certificate
  5. have the system verify the score and download the certificate

The source for that claim page is also public:

So even in the official public flow, these are distinct stages:

  • eligibility and progress state
  • scoring and leaderboard state
  • certificate verification and generation state

That matters, because a learner can be correct about one stage and still fail at a later one.

Short chronology of nearby public issues

Date Surface Public report Why it matters for this report
2025-02-16 Certificate generation Certificate does not support Lithuanian letters Shows the certificate generation layer itself has had concrete bugs.
2025-02-18 Certificate status verification Agents Course Certification Multiple users reported certificate-status failures, and the thread later says the Agents team fixed the issue.
2025-02-25 Unit 1 certification quiz launch / redirect flow AI Agent Unit 1 certification quiz not launching Suggests quiz and certificate app infrastructure could fail independently of learner setup.
2025-03-17 Submission persistence / saved result state Cannot Submit results to Hugging Face Hub Suggests saved submission state and later certificate availability were not always perfectly aligned.
2025-05-10 Leaderboard state vs personal score Leaderboard does not reflect true personal score Weakens the assumption that visible leaderboard state alone proves every downstream course-side state is healthy.
2025-11-18 Unit 4 scoring / file-serving API GET /files/{task_id} returning 404 for every task_id Strong evidence that Unit 4 backend / scoring infrastructure itself has had real failures.
2026-02-06 Unit 4 scoring / file-serving API Hands On API - File download endpoint returns 404 GitHub-side confirmation of the same Unit 4 file-serving failure pattern.
2026-02-08 Quiz / grader endpoint drift [BUG] Unit 2.1 Quiz: 410 Client Error (Legacy API Endpoint) Shows course-side app or grader code can drift behind platform changes and break even when the learner is following the official path.

Why this timeline matters

The important point is not that every one of these reports is the same bug. They are not.

The important point is that the public record shows repeated failures in adjacent parts of the same overall course infrastructure:

  • certificate verification
  • certificate generation
  • quiz launch
  • submission persistence
  • leaderboard interpretation
  • Unit 4 scoring APIs
  • grader endpoint compatibility

So when a learner says:

  • the Agents Course submission succeeded
  • the score appears on the leaderboard
  • the certificate page is the only failing step
  • the problem persists across normal browser troubleshooting

that is already compatible with the public history of this course infrastructure.

What I would and would not infer

I would not infer from leaderboard visibility alone that the certificate claim must necessarily succeed.

I would not infer from a single browser-console message that the precise root cause is already known.

But I would infer that:

  • this is not obviously just a local cache issue
  • the certificate page is only one layer in a multi-step system
  • nearby course-side failures have happened before
  • a verification mismatch, claim-flow mismatch, or certificate-generation-side problem would fit the broader public pattern

Why the official docs themselves point in this direction

The Claim Your Certificate page is already written as a live verification step, not as a static download page. It explicitly says the system verifies the score and then downloads the certificate.

It also says:

If you have any issues with submission please open a discussion item on The certification community tab.

That wording is useful because it implicitly acknowledges that a learner can reach the certificate stage and still hit a course-side problem worth escalating.

What the team should probably check first

If the course team investigates this, the most useful checks are probably:

  1. Which certificate is being claimed

    • fundamentals certificate
    • completion certificate

  2. Whether the account on the certificate page exactly matches the scored account

    • same Hugging Face username
    • same active session
    • same account context used for the final challenge

  3. Whether the backend believes all prerequisites are satisfied

    • Unit 1 completion
    • use-case assignment completion if relevant
    • final challenge completion
    • recorded Unit 4 score above the published threshold
    • expected leaderboard record linked to the claiming account

  4. Whether the certificate verification flow and certificate generation flow still agree on the expected request shape

    • several recent Agents Course reports suggest endpoint or app drift is a real failure class, not just a hypothetical one

  5. Whether the certificate can be generated manually for the affected username

    • if yes, that would point more strongly to a claim-flow problem than to an eligibility problem

  6. Whether there are clustered recent reports

    • if multiple recent Unit 4 learners can reproduce the same final claim failure, that would point much more strongly to regression on the course side

What a useful escalation report should include

If the learner opens or updates a report, the most useful payload is probably:

  • Hugging Face username
  • exact certificate type being claimed
  • exact score
  • leaderboard evidence
  • exact error message
  • screenshot
  • timestamp with timezone
  • browser and OS
  • whether the same failure reproduces in incognito
  • whether the same failure reproduces in a second browser
  • whether the same account is definitely used on both the leaderboard and the certificate page

Bottom line

This is not a perfect one-to-one match with every earlier report, but it is much closer to a known Agents Course certificate / quiz / scoring-flow issue than to a purely local browser problem.

The public trail already includes nearby failures in:

So if the learner is already eligible under the current published rules, I think it is entirely reasonable to investigate the certificate verification and generation flow on the course side rather than treating this as a generic local-browser issue by default.