Preventing it from building up can be done according to the following recommendations by Nintex:

If your environment contains workflows with logic that includes a lot of looping and processing, then each process is noted in the database, even though only the last result is logged in the history list. In this situation, you may want to stop the logging from occurring for those actions.

The following workflow actions trigger programmatic looping and processing.

What do you mean by workflowprogress? If you mean that it logs everything it does here is an example of something you can do:

Say you have a workflow that has a Foreach in it. You can double-click the Foreach. Click on "Common". Then click on "Hide From Workflow Status". If you look in your history after this is run, everything in the foreach including the foreach will not show up!!! That reduces what is stored.

Preventing it from building up can be done according to the following recommendations by Nintex:

If your environment contains workflows with logic that includes a lot of looping and processing, then each process is noted in the database, even though only the last result is logged in the history list. In this situation, you may want to stop the logging from occurring for those actions.

The following workflow actions trigger programmatic looping and processing.

Leif Frederiksen, there is some good feedback from burkslm. If you feel these responses provide a good answer please mark one correct. Or provide some followup if you need more clarification. Thank you for your participation in the community! I enjoy your posts.