Hi everyone,We’re running Nintex workflows on SharePoint Server Subscription Edition (SE), and since our migration, several workflows are not running smoothly. They fail intermittently with a generic “Error Occurred” message. The detailed error states:“The workflow could not update the item, possibly because one or more columns for the item require a different type of information.”This message doesn’t clearly indicate which field is causing the issue. What’s unusual is that if we ask users to delete the file and re‑upload it, the workflow completes successfully afterward.Has anyone seen this behavior on SharePoint SE post‑migration? Any ideas on what might cause this or how to identify the problematic column?Any guidance or troubleshooting tips would be really appreciated.

Question

SharePoint SE – Workflows Not Running Smoothly After Migration (“Error Occurred”)

Forum|Forum|21 days ago
February 20, 2026
3 replies
37 views

+1

Ida.Cheung
Rookie

Hi everyone,

We’re running Nintex workflows on SharePoint Server Subscription Edition (SE), and since our migration, several workflows are not running smoothly. They fail intermittently with a generic “Error Occurred” message. The detailed error states:

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

This message doesn’t clearly indicate which field is causing the issue. What’s unusual is that if we ask users to delete the file and re‑upload it, the workflow completes successfully afterward.

Has anyone seen this behavior on SharePoint SE post‑migration? Any ideas on what might cause this or how to identify the problematic column?

Any guidance or troubleshooting tips would be really appreciated.

+23

Simon Muntz
Collaborator
Forum|Forum|17 days ago
February 24, 2026

Hi @Ida.Cheung,

Welcome to the community,

Does the workflow log show which action the workflow is failing on?
Without seeing logs, I can only speculate on the issue.
I think this is a timing issue.
Your old environment was probably slow, so there were no locking issues for the item.
This is why re-running works, as the timing can be different at different times depending on the load on the server.
Now that you have migrated and everything is faster and fresh the workflow is trying to work on the item while SharePoint still has it locked. Find out what action the workflow is erroring on and place a pause before it. Adding a Commit Pending changes action may also work.

Looking for a Nintex partner to help with your solution? Contact Definiti - https://www.definiti.com.au/