Hello AMD Support,
I’m taking the “AI on AMD” course through AMD AI Academy.
I completed the Hands-On Lab in Module 2:
“Building Your First AI Chatbot” (Jupyter Notebook).
I ran all the cells in the notebook and completed the lab, but the AMD AI Academy course page still shows Module 2 as “NOT STARTED”. Because of this, Module 3 (Quiz) remains locked.
There is no “Complete”, “Submit”, “Finish”, or “Mark as Complete” button in the Jupyter Notebook that I can use to register the lab as completed.
Could you please check my account/course progress and manually update the Module 2 lab completion, or let me know how I can trigger the completion status?
I can provide screenshots of the course page and the completed Jupyter Notebook if needed.
Thank you.
I have the same issue.
I am currently taking the “Introduction to AI Agents” under AI foundations and currently in Module 8: Hand on Lab 1, “Lab: Building A Basic Chatbox With LangGraph”.
I have completed and ran all cells multiple times, saved the progress but to no avail.
Because of this the rest of the module still remains locked.
Hello, sorry to hear this is preventing you from finishing the labs. This has affected most of the users so It is a widespread issue, and I saw an admin confirm it in Discord thread and mention he’s working on it. So you are not alone in this, thanks for the patience.
@Syed_Ridwan @Mohammed-Zahed_Sinan
Hey, just to confirm here - we’re currently investigating this issue and I’ll keep you updated, sorry for the inconvenience!
Hey @Mohammed-Zahed_Sinan and @Syed_Ridwan,
Wanted to inform you that the lab completion tracking has now been restored. Please close existing labs, re-open and complete them again. Apologies for the inconvenience.
Same issue here with “(3) ROCm Libraries PyTorch & AI Frameworks” - module 3 completed multiple times, the course curriculum still flags it as non-started.
Hello @Massimo_Roberto_Scam this issue has been brought to the attention of the admins. Over the weekend, AI Academy underwent a scheduled maintenance. As a result, some of the normal functions on the platform were disrupted. It is being investigated and you will be notified once the issue is resolved, thank you for flagging and thanks for your patience.
Thanks admins for keeping us updated.
Notebook progress tracking depends on the platform being able to see the cell execution events, and there are a few common reasons it cannot.
The ones I would check in order:
Kernel identity. Progress is attributed to the kernel session that launched the notebook. If you started Jupyter outside the platform’s launcher (a bare jupyter lab in a shell, or a kernel left over from a previous session), the execution events go to a kernel the tracker does not know about. Restarting the kernel from the platform UI and re-running the cells is the fix, and it is worth confirming the kernel id changes when you do.
Cell execution order. Many trackers key off monotonically increasing execution counts. If you ran cells out of order, or re-ran a cell so its count went backwards, the tracker can decide the notebook was never completed end to end. Kernel → Restart & Run All produces a clean 1..N sequence.
Autosave versus save. The tracker reads the saved .ipynb, not the in-memory state. A notebook that looks complete on screen but was never written to disk shows as untouched. Check the file mtime after an explicit save.
Output size. Cells with very large outputs can be truncated on save, and a truncated notebook can fail the platform’s completeness check. Clearing outputs before the final save is worth trying if the other three do not apply.
If none of that moves it, the transcript endpoint is the ground truth — if the lesson shows incomplete there while the notebook is clearly finished, it is a write-side problem rather than a tracking one.
For anyone still stuck: AMD confirmed the tracking issue was on the platform side and has been restored. What worked for me was running through the lab sections, then closing the lab and relaunching it from the course page. That updated the tracker. If you ran the lab before the fix, you’ll likely need to re-open and complete it again.