Error: Background message, type:error, message: Assigned to user not a member of Assignment group

MS12
Kilo Sage

I'm running a flow from a scheduled job that is creating a case.

It is supposed to pick Assignment group and assigned to on the case based on the queries in the flow.

I see all the flow variables are set correctly but the case only gets assignment grp.

Assigned to is blank!

 

This is the error I get in the logs: Background message, type:error, message: Assigned to user not a member of Assignment group.

This is not a valid error since the user belongs to the group and I can set it to that user using the form view.

To make things complicated, it only happens in UAT.

Test/Dev works fine with the same flow.

 

I thought maybe if I set assignment group first, assigned to will be saved correctly. But that didn't help.

I am out of ideas to try. Any help is appreciated.

Thanks!

1 ACCEPTED SOLUTION

Hi Rajesh,

 

Thanks for the reply. User was direct member of the group. I fixed it using a workaround. Initially a sub flow was setting the assigned to resulting in this error. I changed the logic so the sub flow sends the assigned to value as an output to the main flow and I set the assigned to in main flow. It worked. So assignment group is being set in subflow, control comes back to main flow and then sets assigned to. Hope this helps someone. 

View solution in original post

2 REPLIES 2

Rajesh Chopade1
Mega Sage

Hi @MS12 

Check user is direct member of group and not via nested group membership. Some configurations not recognized the nested group memberships. 

Check any 'onChange' client script of the 'Assignment group' or 'Before' BR not interfering with flow logic. For this you can create background script and add 'Assignment group' & 'Assigned to' fields. This can help to find the issue, is with flow logic or environment.

 

I hope my answer helps you to resolve your issue, if yes please mark correct & helpful.

thank you

rajesh

 

Hi Rajesh,

 

Thanks for the reply. User was direct member of the group. I fixed it using a workaround. Initially a sub flow was setting the assigned to resulting in this error. I changed the logic so the sub flow sends the assigned to value as an output to the main flow and I set the assigned to in main flow. It worked. So assignment group is being set in subflow, control comes back to main flow and then sets assigned to. Hope this helps someone.