Report a problem from a lab
When something goes wrong inside a lab (the environment never finishes preparing, the terminal keeps disconnecting, a check fails although your work looks right), report it without leaving the lab. The ticket carries the details of that lab, so support can look at the exact environment you are working in instead of asking you for it.
Before you start
Section titled “Before you start”- You are inside a lab: a tutorial, challenge, playground, training environment or assessment.
- If you can, take a screenshot of the problem first. On most systems, Win+Shift+S on Windows or Cmd+Shift+4 on macOS.
Send the report
Section titled “Send the report”-
In the lab’s top bar, select Report a problem (the lifebuoy icon). On narrow screens only the icon is shown.
-
The Report a problem form opens. Under the description, you see Attaching the running lab session followed by the session id. Your plan, your organization, the lab’s setup progress and your browser version travel with it, where available.
-
Fill in Subject, Priority, Category and What happened?. For a blocked lab or assessment, choose P2 — High and the category Lab environment or Assessment.
-
Optionally attach a screenshot: select Attach screenshot, or paste the image with Ctrl+V (Cmd+V on macOS) or drop it on the form. PNG, JPEG or WebP, up to 5 MB.
-
Select Send ticket.
The confirmation shows your ticket number. Select Done to return to the lab: it keeps running while you report. Replies arrive by email, and the ticket appears in the Help Desk of the lab’s organization. See Open a support ticket to follow, escalate or close it.
What to write
Section titled “What to write”A good report answers three questions:
- What were you doing? The task you were on and the last command you ran.
- What did you expect? For example, “the check should pass because the pod is running”.
- What happened instead? The exact error message, copied from the terminal if you can.