Question

Workflow Database growing 3 GB per day (now over 100 GB)

Workflow

Updated February 8, 2016

asked on February 8, 2016

So.. I have got a real problem on my hands. My workflow database is growing by about 3 GB per day. We're not that big a site <50 users and there is no valid reason that it should be growing this way. I've tried the settings under advanced server options and set

Remove reporting data for completed workflows, lifetime 1 day, timeout 300 seconds
remove instance data for completed workflows, lifetime 1 day, timeout 300 seconds
remove unreferenced items from workflow message cache 300 seconds

I've tried shrinking the database in SQL server and that doesn't seem to do anything. Anyway I'm not sure what to do..

0 0

Replies

replied on February 8, 2016

Is it your db that is growing or is it the SQL transaction log? If it is your transaction log, try the links below .

https://technet.microsoft.com/en-us/library/ms345382(v=sql.105).aspx

http://stackoverflow.com/questions/480897/how-can-i-manage-sql-server-log-size

https://technet.microsoft.com/en-us/magazine/2008.08.database.aspx

http://www.sqlskills.com/blogs/kimberly/database-maintenance-best-practices-part-iii-transaction-log-maintenance/

0 0

replied on February 8, 2016

Check the Workflow Statistics Report to make sure that the number of workflow instances is what you expect and you don't have an infinite loop or something like that.

0 0

replied on February 8, 2016

It's the SQL DB that's growing. I found the problem but I'm not sure how to fix it. We have an extremely simple workflow that is hung up on one file. The workflow renames a file based on the metadata contents. unfortunately that one file has tried to launch the workflow hundreds of thousands of times. Each one of those hundreds of thousands has a pile of failed 'rename entry' activities that are erroring out with Entry locked (9014), then it waits and trys again. The default for an entry lock is every 5 minutes to try again. You can actually watch the workflow locking and unlocking in the laserfiche admin console's locked entry.

So now what I'm looking for is the equivalent of this (in bad psuedocode):

Terminate workflow where workflow instance = 147070

(I can't do it through the gui since it's in the thousands of instances and I'm not going to right click on each to hit terminate)

0 0

View 1 previous reply

replied on February 8, 2016

Let's disable the starting rule first so the workflow stops triggering itself. Then modify the starting rule to exclude the user from its connection profile so it will not start on its own actions.

You can search for all instances in the Workflow Designer, select them all and terminate them.

0 0

replied on February 8, 2016

Thank you. There are 550,000 instances, I'm wondering if CTRL-A will handle them all. Is that the best way - through workflow designer?

0 0

replied on February 8, 2016

It should, though it might be slow to respond.

You can also have your reseller open a support case and get a copy of the Workflow Database Cleaner utility which will delete them directly from the database.

1 0

replied on February 8, 2016

ok I will inquire with them for that tool

0 0

You are not allowed to follow up in this post.

Question

Question

Workflow Database growing 3 GB per day (now over 100 GB)

Replies

Sign in to reply to this post.