SCORM Time Out Error: Is anyone experiencing a SCORM time out error (recent as of yesterday)? Short time out periods for time out, customers get kicked out and then loose their spot in the view. We also continue to experience the SCORM 404 errors.
Our customers are very disappointed as the SCORM errors are now growing with the time out error (today).
Any solutions you have been able to implement on your end?
Its the relicensure rush and the customer support calls for both 404 and now the time our have been constant. Any advice is welcomed. We submitted JIRA tickets on these and have been waiting for months on a 404 resolution, now we have a second error.
Our users have been experiencing intermittent Status 400 errors when they try to launch SCORM courses. It seems to occur periodically, and the only workaround is for users to clear their browser cookies. Our current workaround is to provide an FAQ link from the SCORM launch pages explaining how to fix the error. Obviously, this is not optimal from a UX perspective.
The SCORM timeout errors started happening recently. Initially, we thought it might be occuring because of a few slides that contain longer videos, but we are starting to receive reports of very quick timeouts even on short, narrated slides.
The EthosCE team has mentioned that there may be a fix in the works for the Status 400 error.
Has anyone experienced these issues? If so, any advice, workarounds, or fixes?
@allizo We just wanted to chime in and add to your voice that we’ve been experiencing the 400 errors that require the users to try multiple browsers and/or clear cookies as a workaround/solution since we migrated to Ethos. As you mentioned, we too have been guiding our customers to clear cache and cookies (see the PDF that we shared with our customer contact center staff to guide the users; instructions for all major browsers). My colleagues, especially @jadolso has been working with Cadmium (and our IT dept) for a solution for months.
I haven’t tested a course on Ethos over the past week or so, hence haven’t noticed the SCORM timeout (without bookmarking) issue recently. However, we have seen that issue sporadically over the past year or so.
We alerted Ethos to an issue " error 431 - Request Header Fields Too Large" when trying to launch our scorm objects about a year ago. Some of this has to do with the fact that cookies are being set at the domain level instead of our subdomain level, which stems from an issue with how our campus is doing things. If you are experiencing recent issues, however, it could be from the new Cloudflare configuration that they implemented to fend off the bots? We are having AJAX Error HTTP result code: 403 issues and they just started yesterday, so Ethos is exploring the new config to see if they are related.
@JAM We, too, experienced the 431 “Request Header Fields Too Large” issue about an year ago during our migration to Ethos. And thank you for sharing the additional insights about Cloudflare config.