Realming_Grape
Design Dabbler

Workflow Fails when recipient is Security Group

Jump to solution

Hi All

 

We are facing a problem when it comes to setting up a workflow that includes and AD Security group.

The state Machine fails when there is a security group added to the document. 

Example:

1. List column has security Group assigned

2. Workflow fails if Security group is in column.

0 Kudos
Reply
5 Replies
kchaluvadi
Workflow Veteran

Re: Workflow Fails when recipient is Security Group

Jump to solution
Hi, I had similar issue with Nintex for Office 365, but your issue is related to Nintex for SharePoint, try this if not already done.
Go to settings of that column, make sure you select "People and Groups" for "Allow selection of" property.
0 Kudos
Reply
Realming_Grape
Design Dabbler

Re: Workflow Fails when recipient is Security Group

Jump to solution

hi @kchaluvadi 

 

Thanks for your response.

I tried your solution and unfortunately it does not work 😞

 

Kind regards

0 Kudos
Reply
kchaluvadi
Workflow Veteran

Re: Workflow Fails when recipient is Security Group

Jump to solution

Ok, try this:

Go to Security group settings - under Group settings, set "Everyone" for "Who can view this group membership".

WF-GroupSettings.PNG

0 Kudos
Reply
Realming_Grape
Design Dabbler

Re: Workflow Fails when recipient is Security Group

Jump to solution

Hi @kchaluvadi 

 

I tried this now and still the same error 😞

 

This is the Nintex Version we are using

Nintex Workflow SharePoint 2016 - 4.5.2.0
 
Error:
2021-07-29 10:11 AM Error Workflow failed to get user profile for user:c:0+.w|  
2021-07-29 10:11 AM Error An error has occurred in SOP Review.  
2021-07-29 10:11 AM Error For more information, please read this article: http://go.microsoft.com/fwlink/?LinkID=323543&clcid=0x409

 

0 Kudos
Reply
Realming_Grape
Design Dabbler

Re: Workflow Fails when recipient is Security Group

Jump to solution

I Figured it out!

 

in the Flexi Task, under task notification, i was using a lookup and added the Security group.

Turns out, Nintex doesnt like having that lookup in the notification.

 

Thanks for your help

View solution in original post

0 Kudos
Reply