There’s a lot going on behind the scenes of your when you play your course in SCORM Cloud and the debug log is where you find all of that information. In most cases, you won’t need to look at the debug log, unless you’re into that kind of thing, but it’s there to use if something goes wrong with your course. I’m here to show you how to find them, why you use them and how to share them with others.
You can access your Debug Log three different ways: through your sandbox, from the course itself, and a super sneaky way.
Option 1: You can check out the active logs from right inside your course. To do this, you will need to add the navigation bar to your course.
- Pick your course from your Library
- Change your Course settings to allow the Navigation Bar to show up in your course and click ‘Save’
- Launch your course and click through it. Click ‘View Debug’ when you’re ready to see what's going on behind the scene.
Option 2: To access the Debug Logs from your course sandbox.
- Choose your course from your Library
- Choose the session you want to view
- This will open up your saved debug logs. You can also share this debug by copying the URL at the bottom.
Option 3: You can:
1) open the browser dev tools console
2) make sure the frame it’s referencing is the one that contains the player page (not the content) -- there’s usually a drop-down at the top left of the console that specifies this
3) Type Debug.ShowAllAvailableData() and hit Enter. This should bring up the window.
Why would I use Debug logs?
Think of it this way: When you car is working properly, you never lift the hood, but when something goes wrong, that’s the first place you start. Debug logs show you what’s going on behind the scenes and makes it easy for you to pinpoint issues.
Sharing your Debug logs
When you open your course via option 2, you will see a URL on the bottom. Copy that and share it with whomever you wish.
