Can I Double-Submit Results to compensate for latency?

Nov 02, 2023

Howdy,
We have our results slide set to Submit results when the timeline starts, but does anyone know if adding an extra trigger to re-submit those same results again later in the timeline could cause any problems on the LMS side when getting the report from the LMS?

The reason we'd like it to submit again when the timeline reaches X or when an object enters, is for visual confirmation that the results have for sure been sent, because we've had some buffering/timeline skip-ahead issues due to latency problems with the LMS network.

But that same latency has also cause timelines to start fine, but then hang, buffer, then jump ahead skipping time X or the trigger object, so ideally, I'd like to cover many bases by having it Submit results at multiple intervals along the timeline, so it's likely that at least one of those times would make it through and not be dropped by packet loss.

So does anyone know how the LMS (Cornerstone) receives Results; whether each new submission simply overwrites, or would this cause duplicates that confuse the LMS when it comes to generating its report?

Many thanks in advance as always!

1 Reply
Steven Benassi

Hi Jason!

It sounds like you had questions about adding multiple submit results triggers to your course. I'd be happy to share some insight on this!

If your LMS (Cornerstone) accepts more than one status update per course, each completion trigger that the learner encounters will update the LMS with the learner’s latest status.

However, if Cornerstone only allows one status update per course, the first completion trigger that the learner encounters will be recorded by the LMS and the other completion triggers will be ignored.

I would defer this question to our helpful community to see if they have encountered a similar design situation. Hopefully, they can share some feedback as well!