Collecting debug information

When you encounter an error that we need to debug, it is vital to have a so-called kms-unique-id. This is especially true when the error only appears when a specific user is logged on, or when the error only appears through an embedded solution like LTI1).

The kms-unique-id must be fetched from the actual request that generated the error, the id is passed from our servers to your browser as a HTTP-Header, that can be found using the browsers inspection tool.

This video demonstrates how to do in Google Chrome:

When you have found the kms-unique-id you should note it down and sent the support.

LTI - Learning Tools Interoperability®