Check LMS and engine health before investigating a player bug

What this function does and why it matters

Check LMS and engine health before investigating a player bug is part of the Engine Diagnostics and Support workflow in ClassRoom.Study. The function exists to help the right stakeholder move from intention to action without guessing which page, button or record controls the outcome. Use health endpoints and deployment aliases to confirm both the LMS and engine are online before debugging course playback. In daily use this means a learner can understand what to do next, a creator can prepare learning material with fewer support questions, a company admin can manage people and evidence with a cleaner audit trail, and a platform admin can see whether the process is working at scale. For support teams, diagnostics provide a disciplined path from symptom to cause: health, access, key resolution, media status, evidence and logs. For users, this means faster fixes and less repeated troubleshooting.

The benefit is not only convenience. This area protects operational consistency. It makes status visible before a person acts, keeps related records connected, and gives teams a repeatable way to train new users. When a company has many learners, courses, invoices, schedules or live sessions, small navigation mistakes become expensive. A clear manual gives every person the same mental map: where to start, what to check, what each control changes, and what proof should exist after the action is complete. Use this page as the plain-language reference when onboarding new staff, answering support tickets, checking compliance, or preparing screenshots for a branded internal guide.

Benefits and features

• Prevents wasting time debugging content when the service origin is unhealthy.
• Confirms whether production aliases point to the expected ready deployments.
• Gives support a repeatable first check for any classroom player issue.

Step-by-step navigation

Follow the steps in order the first time. After you understand the flow, you can jump directly to the control you need. For training purposes, replace every screenshot placeholder with the exact screen your users will see in production, including the correct company, role or learner context.

1. Step 1: Open the LMS health endpoint and confirm a 200 response.
   Screenshot placeholder for step 1
2. Step 2: Open the engine health endpoint and confirm a 200 response.
   Screenshot placeholder for step 2
3. Step 3: Check Vercel aliases if a recent deployment says ready but the site looks old.
   Screenshot placeholder for step 3
4. Step 4: Continue to route logs or course recovery only after both origins are healthy.
   Screenshot placeholder for step 4

Good operating habits

Work from the smallest panel that gives you the control you need, confirm status chips before acting, and use exports or detail pages when you need an audit trail. If an action changes billing, access, certificates, AI usage, invitations, public content, or live session attendance, pause long enough to confirm the company, learner, course and date context. Add notes where the interface provides them. Use filters before exporting so the exported CSV answers a specific question. When training a novice, ask them to say what changed after each step; if they cannot explain the result, they should return to the record and check the status, timestamp, or linked activity before moving on.