As something of an update… the course-opening-with-syllabus-collapsed behavior seems to occur mostly with courses launched from within a learning plan, whereas if I am accessing those courses independent of the learning plan, the syllabus is open as intended.

haven't followed that specifically but I did notice that when using the option to land directly on the course player page + course auto launch, the user is not always brought back the last object they worked on...seems to be some kind of delay or something that is not being communicated properly back to the LMS...Sometimes I land on the right object but mostly not...wonder if this is related to your issue?

Thanks for the response ​@lrnlab. We’re mostly operating with autoplay off, so I haven’t noticed that. I’ll submit a ticket this afternoon and see if the support folks can assist. Hopefully if the issues are related, they’ll have a solution that can fix them both (fingers crossed).

thanks! and if you can keep this post alive once you get a response from support that would be great.

​@lrnlab Wanted to give you a bit of an update on this. The support ticket we submitted went up to the Tier 3 engineers who were able to replicate and identify the issue. Docebo support indicated that they were expecting to have a fix for the issue released on December 4th. I haven’t gotten confirmation that any such fix was implemented, however in my testing, I have not been able to replicate the behavior.

If it’s not officially fixed, it seems it’s at least closer to being so. 

Thank you for following this up...my guess is they will implement the fix on Dec. 18. Many of our cases are being delayed til that date due the issue they are having with the new notification service and other things like the course player launch...If you don tondi, please update this thread once you see the fix. Thank you.

As an update - the fix has been applied to production and sandbox instances globally, per our Support rep.