User Groups Troubleshooting

Symptom-by-symptom resolutions for the most common User Group and user-segmentation issues. If you don't find your symptom here, double-check the group's Group Type, the read-only Group Conditions on the detail page (the segmentation rules for Automatic groups), and the User accounts the group should be matching.

The Member Count Looks Wrong or Hasn't Changed

Symptom: You added or removed members, or your data changed in a way that should affect an Automatic group, but the Group Members count badge or the Members column on the list view hasn't updated.

Cause: Member counts are derived from a stored procedure that runs on a daily schedule. The count badge in the UI refreshes once per day. Live additions and removals show in the member table immediately; the count number lags until the next refresh.

Resolution:

1. For an Automatic group, open the group's detail page, click the kebab menu (three dots), and choose Recalculate. Once the spinner clears, both the member list and the count are accurate.
2. For a Manual group, the member list is always immediate. The count badge is what waits for the daily refresh.
3. If the count is still wrong after a recalculation, see "A Role's users aren't reflected in the count" below.

A Role's Users Aren't Reflected in the Count

Symptom: A Manual group has a Role added, but the count is much lower than the number of Users assigned to that Role (for example, the Role has 93 Users but the group shows 42).

Cause: The displayed count is the count of distinct Users, after deleted and anonymized Users are excluded. Older portal versions counted entries (one per item added), which produced misleading totals when Roles were involved.

Resolution:

1. Compare the Role's Users in the Role Report. Filter to active, non-anonymized Users.
2. If the User Group count still doesn't match, click Recalculate from the group's kebab menu (Automatic groups) or wait for the daily refresh (Manual groups).
3. For Manual groups, you can add a small known number of Users directly (for example, two Users who are not in the Role) and confirm the count goes up by exactly that amount on the next refresh.

A New Automatic Group Shows Zero or an Unexpected Count Right After Creation

Symptom: You just created an Automatic group and the count is zero, or it looks lower than the number of Users the conditions should match.

Cause: The recalculation runs in the background after save. While it runs, the group's Ready flag is false and the page shows the "the group members are being recalculated" spinner. The count badge will not be accurate until after the recalculation finishes and the next daily count refresh runs.

Resolution:

1. Wait for the spinner to clear and the Edit, Delete, Clone, and Recalculate actions to re-enable.
2. If the spinner persists for an unusually long time on a small data set, refresh the page; the recalculation may have completed.
3. Click Recalculate again from the kebab menu to force a fresh calculation if the count still looks wrong.

Group Conditions in View Mode Show Field IDs Instead of Names

Symptom: The read-only Group Conditions section on the detail page shows internal IDs (long alphanumeric strings) instead of friendly field names.

Cause: View mode renders each condition's Field, Operator, and Value using the field's display label. If a custom field on User, Account, or Contact lacks a display label or has been renamed, the resolved label may revert to the underlying ID.

Resolution:

1. Open Setup > Customization > Entity Manager and verify the custom field has a display label.
2. Reload the User Group's detail page after the field change. The labels should now resolve correctly.
3. If the issue persists on a standard field, contact Magentrix Support.

A Role in a Manual Group Shows "Inactive" Status

Symptom: The member table's Status column shows Inactive for a row whose Type is Role.

Cause: Status applies only to User accounts. The Status cell for Roles should be empty. Earlier portal versions incorrectly displayed "Inactive" for Roles.

Resolution: Update to the current portal version. After the fix, Role rows show an empty Status cell. If the issue persists after an upgrade, refresh the page to clear cached data.

A User Is Missing From an Automatic Group I Expected

Symptom: A specific User who should match the Automatic group's conditions is not appearing in the member list.

Resolution:

1. Open the User Group's detail page and review the read-only Group Conditions and Filter Logic.
2. Open the User's record and confirm every relevant field value satisfies the conditions. For lookup fields (User > Account > Type, for example), verify by record ID, not display text.
3. If the User's data was changed recently, click Recalculate on the group to re-evaluate membership immediately.
4. If the User is deleted or anonymized, they are excluded by design and will not appear in the member list or count.

Filter Logic Refuses to Save

Symptom: Saving an Automatic group's edit returns a validation error on the Filter Logic field.

Cause: Filter Logic must reference row numbers that exist in the conditions table and use only AND, OR, and parentheses.

Resolution:

1. Confirm every number in the expression matches a row in the conditions table.
2. If you removed a row, update the expression so the removed row number is no longer referenced.
3. Examples of valid expressions: 1 AND 2, (1 OR 2) AND 3, 1 AND (2 OR 3). Invalid: 1 + 2, NOT 1, 1 AND 4 when there are only three rows.

Deleting a User Group Is Blocked

Symptom: The Delete action on the kebab menu is disabled or returns an error.

Cause: The Delete action is disabled while the group is in the recalculating state. Other delete failures usually indicate the group is referenced from sharing settings.

Resolution:

1. If the group shows the recalculating spinner, wait for it to complete, then try Delete again.
2. If Delete is enabled but fails, audit the modules referencing this group (Articles, Document Library, LMS, Engagement Pages, Active Pages, etc.) and remove the User Group from their sharing settings before deleting.

Cloning Doesn't Copy Members

Symptom: You cloned a Manual User Group but the new copy has no members.

Cause: Clone duplicates the group's definition (Name, Type, Description, and for Automatic groups the Conditions and Filter Logic). It does not copy the member list of a Manual group, by design, so administrators don't accidentally duplicate ad-hoc memberships.

Resolution: Add members to the cloned Manual group manually using + Add Member. Cloned Automatic groups recalculate from their copied conditions immediately.

<< Managing User Group Members