Yes. We have the same issue. We have had an ongoing open ticket with Docebo as well. Please let me know if you ever received any resolution for this.

Hi @shona.dunn,

It appears that this may have been an issue with the way were were updating our xAPI content. I say appears because, we didn’t receive much help from the open tickets I had when trying to figure this issue out.  

As a workaround to solving the issue, I simply reset the training material in the course management area. However, that was not necessarily the right idea as it erased previous completion information I had to make note of that information and then update it manually. We try to avoid that if possible.

What did work was properly updating the training material. For xAPI content I’ve found per the help article that while you generally upload new/original xAPI content directly to the course, you should then push it to the central repository(CLOR) and make future updates to the training material in the CLOR and push it to the course thereafter. This little piece of truth appears in one location of the Uploading xAPI Content article in the tips and tricks area(literally the last line)

Upon updating the training material as a new version, with a fresh copy from the the authoring tool resolved this issue for us. Unfortunately, if a user opens the content after the update and they had previously completed it, it shows as not completed for the new version. I hope this helps, but being newer to Docebo myself I don’t know specifically that this is the right answer.

Let me know if you have any questions. 

-Jason

Thanks so much for the reply! I received a solution from Docebo, so in case anyone else encounters the issue:

They believe it is a structural issue that can be solved for future users by pushing the SCORM file to the Central Repository, allowing users to take advantage of the Versioning option. This will allow users to be automatically updated to the new version once it has been pushed into the course and will retain the progress information from the previous version in the reports as well.

For any current users with the issue, their suggested solution is resetting users' progress (purging the stored date allows the users to access the current package without issues caused by a structural mismatch or corrupted data).