For some background, we are a training provider for the automotive and aerospace industries. We have a few v/ILT courses that are part of mandated training for engineers to maintain an industry certification. As a result, they need to take training and recertify every few years.
These courses get scheduled often, like 250-350 times per year. We migrated to Docebo about a year ago, and recently finished importing historical session data. Due to internal and external requirements, we store the last 7 years of historical course, session, and enrollment data.
We now have about 1500 sessions under our largest course. Learners who are enrolled in a session of this course are experiencing 15-30 second load times when they click on the course tile on their homepage and attempt to load the session details. There’s no indication anything is happening, no loading bar or hourglass, the middle part of the screen is just blank until the sessions load in. It’s a pretty sub-optimal user experience.
After working with Docebo support, they indicate the delay is caused by number of sessions in the course.
The suggested workaround is to split the course annually or quarterly. Not only would this complicate historical reporting, it’s not really an option for us due to the LMS’s integration with our other business systems (ERP, ecommerce website, etc.).
As a novice, looking at the API calls, it appears the page is loading ALL sessions, then only showing those the learner is enrolled in. It seems like an obvious solution is to use a different API endpoint, one that only pulls session details for those the learner is actually enrolled in, right?
I’m curious, has anyone else run into this issue when there are a lot of sessions in a course? Were you able to find a suitable workaround other than multiple courses? I couldn’t find any mentions of limit on sessions in the knowledge base or help docs. I’m curious what the best practice is, should we stay under 500 sessions? 250?
Am I in left field in thinking this should be fixed as a bug in functionality, rather than something that I submit to the ideas portal? If my car stopped working reliably after I hit 10,000 miles, I’d probably want to address the underlying issue rather than keep buying new cars.