What job add or removes role(s) from user(s) of group and why has it been queued?

cherylbrownlee · ‎08-13-2020

Adding roles to a group is usually immediate, but today in a non-Prod instance, this information banner is popping up and the roles are not adding. The group(s) in question have less than 10 members and the role being added is not multi-tiered. It has been over an hour (I went to meeting) and the role isn't there. Other roles on other groups have worked, but this message always appears. This is not a new role.

Where is this 'job' and why isn't it running/completing?

Tiffany6 · ‎03-23-2022

Hi yes, we had to open a HI ticket and SNOW gave a workaround, stating that that's how it's supposed to work... here's the response.

"I have completed my investigation on this issue and have raised a problem for this (PRB1547123) which is now associated to this case.

The cause of the issue is a combination of two settings:

1) The admin role does not have sn_hr_core.admin role in the Contained Roles on your instance:

{link to oshkosh instance}

2) The system property: glide.ui.schedule_slushbucket_save_for_group_roles is set to true.

As a workaround, to add a user to a group with HR roles, follow the steps below:

1)Set the system property: glide.ui.schedule_slushbucket_save_for_group_roles to false
2) Add the user to the group
3) Set the system property: glide.ui.schedule_slushbucket_save_for_group_roles to true
4) Clear the cache for the system property to take effect."

In summary: For us, it's only happening to my HR groups and groups with roles.

In the environment, go to sys_properties_list.do. Find glide.ui.schedule_slushbucket_save_for_group_roles - should be set to true. Open it and set it to false.

Then make the updates to your groups. Refresh the page to make sure the users were added properly.

Return to glide.ui.schedule_slushbucket_save_for_group_roles again and set it back to true.

I hope that helps. Good luck,

View solution in original post

Cameron Wilson · ‎04-15-2022

Thank you for this Tiffany. We just noticed this as well for HR groups and I couldn't figure out why. This worked for us so will remember this for future additions until ServiceNow corrects it.

Deepak_J · ‎05-22-2023

This was helpful and I was able to add required role per provided guidance above.

However role which I was adding, wasn't relevant to HR role, I was adding SAM role.

Oliver Saxon · ‎11-30-2022

Another affected customer here.

The workaround above isn't working for me. We're on Tokyo release.
Does anybody know of a way to switch this "feature" off? I don't really understand the benefit or the context to it and it's a bit strange for ServiceNow to enforce this type of change.

Umesh3 · ‎02-02-2023

Same issue for me in Tokyo release. any suggestions please?

cameron_s · ‎02-17-2023

Same issue with me on Tokyo release - went through the steps multiple times and no luck.