Hi, over the weekend my workflow started to error out at the following action. I have no idea why it started failing all of a sudden. When approvers go in to approve the task, they are able to approve it however the status of the workflow shows up blank and it errors out with “The workflow could not update the item, possibly because one or more columns for the item require a different type of information. Access Denied”. Things to note:The current workflow task history is hitting 55000+ items which does surpass the threshold. I will work to get the task item count below the threshold. Additionally, I have provided the group of approvers with Contribute access, it was previously just member access. I have also tried to add a commit pending changes before the “Start CreateRequestNum workflow” and this hasn’t helped in anyway The workflows started erroring today as soon as someone approves the request, it restarts the workflow and errors out at the following action. See second picture.

Nintex On Premise - The workflow could not update the item, possibly because one or more columns for the item require a different type of information.

Hi, over the weekend my workflow started to error out at the following action. I have no idea why it started failing all of a sudden. When approvers go in to approve the task, they are able to approve it however the status of the workflow shows up blank and it errors out with

“The workflow could not update the item, possibly because one or more columns for the item require a different type of information. Access Denied”.

Things to note:

The current workflow task history is hitting 55000+ items which does surpass the threshold. I will work to get the task item count below the threshold.
Additionally, I have provided the group of approvers with Contribute access, it was previously just member access.
I have also tried to add a commit pending changes before the “Start CreateRequestNum workflow” and this hasn’t helped in anyway
The workflows started erroring today as soon as someone approves the request, it restarts the workflow and errors out at the following action. See second picture.

Page 1 / 1

Hi, try adding pause action.

Hi,

I have added a pause, I have also added commit pending changes after any action that updates or changes a value in the SharePoint list. Still no luck.

Updated issues:

The workflow errors out sometimes, but then sometimes it also completes and restarts the workflow again without any errors. So basically users get duplicated emails and get asked to reapprove.

I come across this issue A LOT. Nintex support seemed to think the issue was due to a variable not being set before being used to update an item. There are two different queues for actions and it is possible the update item action is reached before the set variable action (even if the update item action is placed after the set variable action in a linear fashion). If this theory stood, then a commit pending changes action before the update item action would force the set variable action to execute. That does not work for me, however.

Please let me know if you figured this out. This issue is causing critical failures in almost everything we have used Nintex for.

Hi, unfortunately, I have not figured this out yet. Thankfully we are migrating from Nintex to the Microsoft Power Platform.

But, I did find that it works, if you resave the workflow with a new name and turn the original one off. It seems as if the workflow corrupts itself after any change is made to it. Try saving it with a new name and turning of the original one. I know it isn’t the best, but it helped me alleviate all of the failed workflow emails.

I’ll give that a try right away! Thank you for the suggestion. Any hope is better than nothing We have had nothing but problems with Nintex On Premise.