IIf you are a SharePoint admin and suddenly notice that your Nintex Workflow page is not loading, you are not alone. You may also see NeedUpgrade=false appearing in the URL, but that parameter is not the cause of the problem. The real issue lies elsewhere: a required list can no longer be accessed and Nintex cannot initialize the workflow page as a result.
Why the Workflow page fails to Load
In most cases, when you see NeedUpgrade=false in the URL, it simply means Nintex has already checked and confirmed that no schema upgrade is needed. The parameter itself is harmless.
The page fails to load for a different reason entirely: SharePoint cannot access a list that the workflow depends on. Because that list is unavailable, Nintex cannot initialize the workflow page, regardless of what the URL parameter says.
Real case with two different outcomes
I recently worked on two similar sites, and the results were different.
Real case with two different outcomes
First site
On the first site, I deactivated and then reactivated the Nintex Workflow feature. As a result, SharePoint re-provisioned the internal configuration and the page loaded correctly again.
Second site
However, on the second site, the same action did not fix the issue.
So, I investigated further using ULS logs with appropriate filters. I quickly found errors indicating that a list had been deleted.
Next, I confirmed this using PowerShell. Specifically, I checked whether any list matched the GUID from the logs. However, no list existed with that GUID, which confirmed that the list was permanently deleted.
What actually broke
At first glance, you might suspect the Workflow History or Workflow Tasks lists. However, in this case, both lists existed and worked correctly.
Instead, the issue came from the specific list associated with the workflow, which no longer existed. Because of this, Nintex could not load the workflow page, even though the system kept returning NeedUpgrade=false.
Why feature reactivation sometimes works
Feature reactivation works when the problem is within Nintex’s own internal configuration lists. In that case, SharePoint re-provisions them and the page loads again.
However, if the missing list is the actual SharePoint list the workflow was built on, reactivation cannot help. That list belongs to the site’s content, not to Nintex’s internal setup, and no feature toggle will recreate it.
As a result, the first site recovered, but the second site did not.
What I did not do
You might consider updating the mapping directly in the Nintex database. However, I strongly advise against this approach.
- Nintex does not support it.
- It is risky.
- It can break other workflows.
Moreover, in this case, SharePoint Designer showed only a simple list workflow. Therefore, modifying the database would not make sense.
How to fix the issue safely
First, check the ULS logs and identify the missing list GUID.
Then, use PowerShell to confirm whether the list exists.
If the list is missing, restore it from a backup. Otherwise, recreate the list and rebuild the workflow if necessary.
Need help fixing this issue?
Experiencing a Nintex Workflow page not loading? Don’t waste time guessing. Identify missing workflow dependencies, validate your configuration, and fix the issue safely.
Need expert help with SharePoint or Nintex issues?
Contact me here
