Does sounds odd….Could it be linked to the new feature that will unregister inactive/expired users? I know you have to deliberately turn that on but it might be worth a check. Hard to say without seeing your data, data rules, etc.

Hi - yes we thought that too, but we put that live over a week ago and its never unenrolled users like this… so we thought it can’t be that? Unless, there was a weird glitch last night in our HR system that it deactivated all users and then reactived them…? 

maybe worth checking…

This is in the audit log

{"course_id":342,"course_name":"Twelve Months Listening Group","session_id":636,"level":"learner","status":"subscribed","enrollment_date":"2024-07-30 08:06:13","enrollment_date_begin_validity":null,"enrollment_date_end_validity":null,"subscribed_by_id":16665,"reason":"user_deactivated"}

But then there is nothing which ‘reactives’ users, and everyone is active, no account has been deactived…?

Sorry are you saying the all your users are active and the audit seems to be wrong? or that the active user was unregistered from their session because they were perceived to be inactive (this is what you refereed to above as a potential bug?) the audit does have options to see whether a user(s) was deactivated/reactivated...would that help

Hey,

active user was unregistered from their session because they were perceived to be inactive.

I’ve checked the audit log and there is nothing there for re-activting users, just a small handful of deactived users who have left the business…

So it’s not deactived the users, but it’s removed them from sessions because it believed they were deactived…

Still no reponse from the ticket we raised this morning and now getting worried its going to happen again tonight..

Support is usually pretty timely but if you feel like this is urgent, you should probably reach out to your account manager...

@CharlieCromp1 I’m having the exact same thing happening! I have ticked the “Automatic disenrolment” box in the course shell, but ACTIVE users are being disenrolled.

@admin_mhshomes  - we haven’t found a fix yet… but what we’ve had to do is untick all the ILT courses with the Automatic Disenrolment. We tested by leaving 1 course ticked - and the next day it had disenrolled them again… so thats causing it. We’ve lost all our data though - so we’ve no idea on how many people have booked onto sessions, and it means other people can now book even though it might have been fully booked - we’re in a right mess. Hope it’s not impacted you too badly

@CharlieCromp1 I’ve just done the same.  Luckily, it appears to only be one course affected because that’s the only one I had ticked!  And I had names on a spreadsheet as back-up (you can tell I don’t quite trust the system), so I’m just manually re-enrolling everyone.  I’m sorry that your experience has been a bit more disastrous.

It just seems so stupid to have that ‘Automatic disenrolment’ as an option when most people’s automation will probably involve deactivating and reactivating users (by the looks of it).  I wasn’t involved in creating the webhook with our HR system, so I didn’t know this was the case until now.  The feature in itself would be useful, if it worked, because of course we’d want deactivated/expired users to be disenrolled in order to free up space for others.  Docebo have got to fix it.

has anyone opened a ticket to ask if this is a bug?

Yes - finally got a response - fix in place for the 21st Aug

@lrnlab @CharlieCromp1 

Same - response below:

“After review, I found that the development team has identified this issue and it seems to relate to rules running for automations, a task has been  created to investigate further.  I will attach this ticket to the related development task so you will receive automatic updates as they are available. I will continue to manage this ticket and will also provide you with additional information as soon as I receive it.”

Thank you for following this up!