Groups

We have also had similar experiences. It is pain staking as we are now constantly having to monitor the AI groups to assure people are not granted access to prohibited content.

@Sophie - what are the criteria for the groups where this is occurring? Is it all of your groups or just ones with specific criteria?

I had an issue a few weeks ago where my group enrollment rules weren’t being triggering so that learning plans weren’t being allocated accordingly. After launching, I would have to go to my LPs and check by reassigning them. 1 out of 3 times it hadn’t. I had reported it and it’s better now, but I still check. 

Yea, enrollment rules are interesting. You have to create group, but not add users. Then create the enrollment rule, then go back and setup the automatic group for users to come in or add users to the manual group for the enrollment rule to work. I know I screwed up a lot at first. Glad to hear it is work for you now.

Can you share a specific example? It would be helpful if you could supply the rules you’ve built and what the expected behavior is. 

If users your rules aren’t targeting are adding users to those groups then it’s likely a bug but the only way we can help is if you could share some screenshots of the conditions you’ve used to build those groups. 

Can you share an example as well? The behaviors being described sound like a bug. 

We created groups using our branching structure so we could modify who has access to channel information and enable coherts for the interactions in the Discover, Coach and Share. We just found some groups were not auto-populating. If it occurs again, I will open a ticket to better track the situation and occurrences. We recreated the AI groups being impacted (just did the same process again). Since no additional users have been added to check for this happening again.

@emily.mason - it would be interesting to know the criteria / rules for the groups that were not populating or having issues.

Meaning was it something stable like branches or was it related to specific enrollment status that may fluctuate.

Thanks everyone. It's good to know that it’s not just us,  although I wish is wasn’t anyone. 

The criteria we use for the Automated groups are branch based, but this information is coming across from our HR system correctly as people are being put into the correct branches.

I do like to solve a mystery,  but I could do without this one, especially as it is so random. 🕵🏻

 
Just to be clear is the only rule in this situation the branch location? It’s not branch AND another condition? We still haven’t seen any of your conditions to be able to truly evaluate whether this is a configuration issue or a bug. 

It’s also worth noting that group rules process asynchronously from branches so you might be experiencing lag due to other actions within the platform. 

It sorted itself,   but it has now done it again.  This time it has booted off the group most of the people who should be in it (around 1400 people) according to the branch based conditions only  - and added over 2000 who should not be in the group?  All very strange.