Hi @sns ,
Whether the user who triggers the workflow is in a nested AD security group of the SharePoint group?
If it is true, please check as follows:
- Make sure User Profile Service is up and running.
- Make sure workflow initiator has a user profile associated.
- Make sure the Security Token Service App Pool has the Load User Profile property set to True as shown in the image below:
Then recycle the Security Token Service application pool and run full user profile sync to compare the result.
If all the above ways do not work, please check the ULS log with the Correlation ID for more information.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.