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

cherylbrownlee
Tera Contributor

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?

find_real_file.png

1 ACCEPTED SOLUTION

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

14 REPLIES 14

Michael Kaufman
Giga Guru

One idea is the group is possibly a parent of many child groups?

I see this KB Article used to have that text in the title

https://hi.service-now.com/kb_view.do?sysparm_article=KB0636107

find_real_file.png

 

Tiffany6
Tera Expert

Cheryl, 

 

Did you ever find a solution to this? This just started happening to me this week.. 

 

bclemen
Tera Contributor

This exact issue started happening to me yesterday in all of our instances, any solution?

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,