Forum Discussion
LSR issue with EDGE
Hello everyone,
I wanted to bring to your attention an issue that one of my clients is currently experiencing with their Learning Management System (LSR). The problem arises when they attempt to utilize SCORM files generated by Articulate 360. Specifically, the issue seems to be browser-related. The LSR functions seamlessly when accessed through Google Chrome; however, when accessed through Microsoft Edge, users are being logged out every 5 minutes.
Browser Compatibility: Which version of EDGE Articulate is compatible with??
is it compatible with Version 117.0.2045.47 (Official build) (64-bit)
Your insights and assistance in resolving this matter would be greatly appreciated.
Thank you
Hello Coursinity Scorm,
Happy to help!
I'd like to look at two things to troubleshoot the behavior you're experiencing. There's a chance that the behavior could either be LMS related, or caused by a policy that's being implemented on your Microsoft Edge browser, so I recommend doing the following:
To test if the issue is LMS related, try uploading your course in SCORM Cloud and accessing it from there using Microsoft Edge. If none of your learners get logged out, we can confirm that the behavior is specific to your LMS.
If you are able to replicate the behavior in SCORM Cloud, try asking your IT staff if they have any company or organization policies being implemented on your Microsoft Edge browser that could cause active sessions to be automatically logged out. They may need to adjust certain policies by implemented by the IT staff.
If no policies are being implemented and you are able to replicate the behavior in SCORM Cloud, would you be willing to share a copy of your project file here or in private by opening a support case so we can take a closer look at what's happening? We'll delete it when we're done testing!
- Jürgen_Schoene_Community Member
Microsoft Edge, Google Chrome and many others have the same html browser integrated
However, there may be a difference between these two browsers, triggered e.g. by different company group policies or different installed addons