A request to record your progress in the Learning application has failed

Jan 21, 2022

I'm having a problem with the success factors lms giving me this message. It's frustrating in that it seems as though, everything I'm doing in my modules seems to be the same as before. I'm getting this error now when the exit module button is pressed. The results are being tracked properly in the lms, I'm just getting this popup. I have tried about 10 different changes to my output methods but it keeps coming up. I'm using scorm2004, 4th and have tried it with both methods of completion: when the learner has completed a quiz and using the complete course trigger.

" A request to record your progress in the Learning application has failed.  Please check your internet connection.  If the issue persists, reach out to your internal support organization for further assistance."

17 Replies
Jody McGurk

Hello all, we are experiencing the exact same behaviour. Through testing we also identified the suspend course/exit command being the trigger for the problem.

We have also seen this behaviour in old content from our LMS which has not been updated. This points to the issue being with SAP, possibly from the last product release we had in November.

We have spoken to someone at SAP this week who is escalating the issue to the product engineers.

David Broughton

We had the same problem at our company.  Has anyone heard of an SAP patch that might resolve this problem?  I see Jody McGurk has a ticket that is being escalated.  Jody, have you heard anything since then?  I've created an SAP ticket but they don't see any hint of the error in the SAP logs, and we are having difficulty reproducing it (even when same person takes the same course from the same machine)...

Jody McGurk

Hi David, we are making little progress with SAP. They are trying to suggest we are causing the error due to data being sent the LMS. We have highlighted the fact this is affecting courses which have worked fine for a long period of time until the recent update. We are still awaiting any meaningful reply or advice. I will post an update here if we have any progress.

David Broughton

Jody, thank you so much for your response.

For us, the training completion is actually recorded correctly.  The users see this error and get confused though (e.g., take the training a second time, etc.).  Normally with SAP we get traction on issue resolution by doing a recording of network traffic during a session where the issue occurs (e.g., open Chrome -> Developer Tools -> Network tab, record error & download HAR file to send to them).  However, in this case we are not able to reproduce the error, and thus are unable to get a recording of it.  One of the things we tried doing to reproduce is having the same user take the exact same course  / content on the exact same machine / browser; the second time they took it, there was no error. 

We thought it may be a timeout, so we took the same course that the user reported as failure and waited longer than the "keep alive" setting.  The error did not occur and we did not time out.  (An interesting side item is that the SAP "Delivering Structured Content" guide says that if the network trace, as described above, shows "checkStudentAction.do", then the problem is not timeout.  And our trace showed that at the exact "keep alive" time.  So, at least for our test, that was not the issue.  Of course, we can't confirm this is not the problem for users actually experiencing the problem because we can't reproduce it.

You indicated your testing revealed the "suspend course/exit command being the trigger for the problem".  Would you mind to share how you determined / found that?

Our SAP ticket has only now (after pressing with our Customer Service Manager) started getting traction.  I'll repost if they find / share anything meaningful.

Mata Henry

I find this post very intriguing. I dont know if its worth anything or related, but..
We've encountered non completions with SuccessFactors (SF) ever since launch a year ago. It seems SF times the user out if no data is passed back to it within a specific time frame. If the user/content doesnt pass anything to SF within 15 minutes, its starts a 15 minute count down to expiration. After expiration, you can still be completing the online and not realise you've been timed out. If you use the popup window to deliver your course, you wont see the message warning you of a countdown. Do you see a message such as this @Video Nexus?

We made some SF system changes - unwillingly, but had to.

  • "contentStructurePageExpireDuration" – which we changed from 120 (2 mins) to 600 (10 minutes) to try keep the page duration longer.
  • "contentStructurePageKeepAliveInterval" change from 120 (2 mins) to 30 (30 seconds). We wanted to try keep the connection more frequent.
  • Even though we extended the user session in SF (to avoid timing out the user), it gets overwritten by the overarching system - which I dont understand.

So there seems to be three sets of running timeframes that can affect a user. I've tried numerous times to replicate an issue and its almost impossible.

  • We therefore no longer use storyline files in large/substantial amounts. They are nested iframes within a nested iframe, so we think are 'black holes' to SF, and possibly therefore trigger the system to time out and produce non completions
  • We no longer use videos that play longer than 5 minutes (usually max 2 minutes). Are a black hole too it seems.
  • We publish all our onlines and quizzes now in Rise and get no issues from quizzes anymore.

Admittedly, we still use a basic SCORM 1.2, but that will change as we need more data.

So, I am very nervous about our pending upgrade too and hyper keen to see what others wins may be here. Sorry if I'm a little off track, but feel like my sanity is sometimes at risk with SF.

Jody McGurk

We have made some progress with SAP on the popup issue. They have identified the issue has arising during the 2111 feature update and have confirmed it is not related to the course content/code. They have indicated they intend to have the issue resolved in the 2205 system release. They have also said their is a possibility it could happen sooner as part of a system 2111 patch. They are going to keep us updated on progress.