Forum Discussion
Timestamp with a future date posted in LRS
We’re seeing a fairly large number of Storyline 360 courses published for Tin Can pass a timestamp that is a future date to our LRS (e.g., a date in May for a course completed in April). It appears this incorrect timestamp is impacting time-in-training reports. These are courses built by different customers of ours, who tell us they are not using a timestamp variable or consciously adding a timestamp to these courses. Is this a known issue to Articulate? If so, can you give us guidance on how to correct the course files?
Hi Randall!
It sounds like all the courses are impacted by the incorrect timestamp! Let's start with understanding if it's a setting in the LRS that we can configure.
The first step is to test your published course at SCORM Cloud and compare the results with your LMS.
SCORM Cloud is an industry-standard testing engine, and although “SCORM” is in its name, you can also use it to test AICC, Tin Can API, and cmi5 content. (Click here for AICC testing instructions.)
If your content works properly at SCORM Cloud but not in your LMS, open a support case with your LMS provider to troubleshoot the issue. Your LMS provider may request a debug log to help identify the problem. Click here to learn how to generate a debug log.
If your course doesn’t play correctly at SCORM Cloud either, send us your project file for review. We're happy to help!
I have the same problem! A course that is showing it was completed in the future! Did you get any leads? It's been an year now.
Hi jugal,
Thanks for reaching out, and I'm sorry to hear you're experiencing a similar issue. We're happy to help!
Have you tried testing in a different LMS environment as my teammate Lauren recommended? Here's a tutorial that'll walk you through the process of testing in SCORM Cloud.
If your course doesn’t play correctly at SCORM Cloud either, send us your project file for review, and we'll help troubleshoot.
