Reading your capstone result and fixing a fail

What the result page shows, the automatic-fail triggers, and how to fix the most common failures before your second attempt.

After you submit, the result page updates on its own as the submission moves through queued, scoring, and a final passed, failed, or error.

The result shows a score for each rubric dimension with quoted evidence from your repo, so you can see exactly what was found and what was missing. If you pass, your certificate is issued.

Automatic fails

Any of these fails the submission regardless of score:

  • The repo is private.
  • Secrets or real personal data are committed.
  • The repo is an unmodified fork of the starter.
  • There is no README.

Most common fixes

Secrets scan flagged a file you know is safe. This is almost always committed Terraform plan output, which can contain values that look like keys. Remove it from the repo and its history:

echo -e "plan.json\nplan.txt\n*.tfplan\n.terraform/" >> .gitignore
git rm --cached plan.json plan.txt
git commit -m "Remove plan output"
git push

"Missing README". Rename the file to exactly README.md at the repo root.

Low score on one dimension. Re-read that dimension on the CGE-P rubric or CGE-AZ rubric and compare it line by line with the evidence quoted in your result.

Status shows "error"

Something broke on our side. Errored submissions do not use an attempt, so you can resubmit. If it errors twice, email hello@grcengclub.com with the repo URL.

Appeals

If you believe the grading is wrong, email hello@grcengclub.com with your repo URL and which dimension you are appealing.

Last updated 2026-10-18

More in Exams and capstones

Still stuck?

Email hello@grcengclub.com with the email address you use for the Academy and a screenshot of what you see. For lab and study questions, the #studygroup_cge_certs channel in the Club Slack is the fastest place to get an answer.