Hi everyone,
I’m dealing with a frustrating issue on Google Skills, and I’ve been going back and forth with Support, but I wanted to see if anyone else here is experiencing the exact same technical bug.
The Problem
When trying to access specific labs and non-PDF lessons, I consistently get a “We’re sorry, but something went wrong” page.
Checking the network data, the GET request to the lab template (e.g., /course_templates/754/labs/597888) throws an HTTP 500 Internal Server Error. The most telling part? The “Waiting for server response” stalls for exactly 31.1 seconds before ultimately failing.
more details in drive folder: technical-issue-google-skills
Troubleshooting Already Performed
Support keeps suggesting browser session conflicts or network issues, but I’ve completely ruled those out. I have replicated the exact same 500 error across:
- Different OS: Windows 10, Windows 11, and Ubuntu Linux 26.04 LTS.
- Different Browsers: Chrome 146.0, Chrome 127.0, Chromium 147.0, and Edge.
- Standard Steps: Incognito mode, cleared cache/cookies, different networks.
The Key Discovery (Account Conflict Hypothesis)
To prove it wasn’t my local setup, I did an isolation test: I accessed the exact same lab direct link in Incognito using a different email account. It loaded perfectly without the 500 error (prompting for credits, as expected).
This confirms the issue is possibly a backend entitlement or synchronization conflict specific to my profile. My account is currently enrolled in multiple programs simultaneously:
- Google Skills Starter
- Google Skills Arcade
- Google Skills European University Challenge
- GEAR Program
It seems that when the backend attempts to validate my access rights across these overlapping enrollments, it triggers a severe timeout or deadlock. This explains the 31.1-second delay before the server gives up and throws the 500 error.
My Question to the Community
Are any of you enrolled in multiple overlapping programs and experiencing random 500 errors on labs? If so, did you find a way to successfully escalate this to the support team instead of getting the standard “try a different network” response?
Any advice or shared pain is appreciated!
