@usharamanamma ….It seems you're writing lot of rows into the SharePoint and there is a chance that your SQL table is getting locked. Also, try below things:

1. Use Commit Pending changes action after your create/update the item in your list


2. I would recommend to schedule this workflow to run off hours


3. Also, put a counter inside the for loop, let's say 30 or something small now every time you create an item in your for loop, reduced it by 1.


4. Put a Run IF to check if the counter reached 0, if it's then inside Run If:
   
   1. Put a pause for a minute
   
   
   2. Reset the counter to 30 or whatever you're setting (but make sure it's not too big #)
   
   

Hello Kunal,

Thank you for the reply.

For now I am only looping foreach item and logging history to check how many rows processed. I want to check first how much time it might take. So didn't use commit . But used pause. Even then there is no luck . Sometimes at pause , it's erroring and sometimes after pause after sometime it's erroring. 

So not able to understand how to fix this. Normally how many records can a Nintex workflow process? What are the ways to fix this  as it erroring even at pause?

Thanks 

@usharamanamma pause action is based on the timer job so for each iteration, it might delay your time too. Also since you're querying the SQL table and it's returning a lot of results, there is a chance you may have connection issues too.

There is no set # of records you can process, various factors play a big part in it e.g. Connection time with SQL, timer jobs, # of workflows timer job processing, resources on SQL and SharePoint servers, etc.