Latency in TinCan responses

Aug 17, 2015


We using TinCan API to export responses from Articulate Storyline.

Articulate via TinCan sends its signals asynchronously. So if in a given frame, we are sending multiple responses at once ( in one case, we send up to 15 in one frame ), the user gets to the end and closes out of the window before all those signals have properly been consumed by the LRS.

Questions :

1. Is it possible to somehow confirm that the responses have been consumed by the LRS before allowing a user to continue?

2. Are there better wrappers other than  TinCan that allow us to do this?


1 Reply

This discussion is closed. You can start a new discussion or contact Articulate Support.