Hi, currently we are having a scenario where we are using lazy approvals.
In a flexi task, we have enabled lazy approval.
The approver recieves an email with lazy approval code as well. When he replies to the email, the corresponding task in the tasks list gets completed. Outcome = Approve.
But the workflow fails at the lazy approval step. when i check in the 'View Workflow history - it shows the message -
Unauthorized attempt to update workflow task by
i:0#.w|<domain>\<userid>,<emailaddress>. The response has not
But the same user is able to approve the workflow task directly from Tasks list, only with lazy approvals, the flexi task action is failing.
note: the task list item gets outcome set to approve/reject. only at the flexi task action, it fails with the above error.
Can you please support?
NIntex workflow version : Version: 126.96.36.199
Awaiting your reply.
Solved! Go to Solution.
Sorry to hear about your issue. Just a quick verification, in the error message does it provide a user's information and you simply just removed that your post here? And if so, does it match the expected user?
Yes, It does display the user information. The exact error message is "Unauthorized attempt to update workflow task by i:0#.w|. The response has not been recorded”.
and yes, it matches the user's credential.
When you the admin tries to approve through the UI it works fine?
But what if the user who had the issue with LazyApproval attempts to approve through the UI, do they get the same issue?
If both are true, then the issue lies in the permission settings on the Workflow Task list.
The user who is approving the request was given full control to the workflow tasks list, apart from that he was the site collection administrator. He is able to approve it through UI but with lazy approvals he gets error.
Can you help me explain why the user ID for each note in the history is from system account? was the workflow started by the system account? Was it published by the system account?
I would recommend to publish and start the workflow as non system and see if there is a difference.