We are using Nintex Forms and Workflow 2013. Users are experiencing in excess of 20 secs load time when acceding a "simple" assigned approval. Rest of the forms load es expected, only the task approvals are slow in loading.
Try using exclusive Task and History lists for that workflow.
Create a new task list and a new History List and configure your workflow to use those new lists.
We have a separate tasks lists and History lists for each of the tasks being generated from the workflow.
To open a Task form it is taking 30 seconds. in that 25 seconds are spent on SQL side.
Following method from Nintex is consuming 11 seconds to execute, which internally calls a SQL procedure named "proc_GetWorkflowDataForItem".
It would be good if Nintex let us know what is best practice to handle this issue.
I have raised a support call with Nitex.
We may want to wait to hear what support responds with as they will have the opportunity to see your system. But I would review before hand the number of items that are in the task list and history list.
If you are building several workflows on a single site, and keeping the default settings for assigned task list and history list, then there is the potential that the lists have a large number of items. Large in number means greater than 5000
We have SharePoint 2013 On Premise and Nintex 2013 and the forms are extremely slow to load. Sometimes up to 30 seconds to open the form. Our users are starting to complain about the slowness. Does anyone from Nintex have a solution or response?
As other forms seem to work fine if might be good to reach out to Nintex support. They can analyze the list and the form controls and might have a clue what causes the performance breakdown.
Any other updates on this issue? We have some forms that have a Time to First Byte (TTFB) of over 30 seconds, while the rest of the site is snappy. Our open ticket with Nintex Support isn't helping other than the standard "Your form is too long, break it into pieces...".
I used to be a real advocate of Nintex Forms and Workflows using it with SharePoint On Premise, but if I had know how bad the OnLine version was....I would not have moved. It takes twice as long to create the workflows and half the basic actions no longer work! If Nintex do not get their act together we will look at another solution!