Question

Workflow is not saving completed activities more than three days old

Workflow

Updated December 21, 2016

asked on December 19, 2016 • Show version history

I have a client where the advanced server options for workflow were set up like the following screen shot, but when they did a search on workflow activities, they only saw activities from the previous three days.

I changed it to retain for 29 days, just as an initial troubleshooting idea, but I still am not seeing any change. They just looked at it, and though it should show all the way back to 12/12 the most recent activity they have is 12/16.

When I looked at the search on 12/15 last week it only showed records for the three days before that.

The client ran a search going back two months, and found a couple of workflow runs on 11/19, but nothing between 11/19 and 12/16.

Is it possible for the Workflow database to get corrupted in a way that causes this, or is there some obscure setting outside of Advanced Server Options that I'm unaware of?

0 0

Answer

SELECTED ANSWER

replied on December 21, 2016

No, reinstall won't change anything, the settings are in the database. I'd try running a statistics report to see if any workflows actually started in the timeframe you're looking at.

Beyond that, probably the best course of action would be to contact Tech Support with a copy of the Logs folder so we can take a closer look.

0 0

Replies

replied on December 19, 2016

I wouldn't necessarily think corruption just yet. Did you check the error logs? Maybe the server couldn't connect to the database and didn't start any instances during that time.

When you say "activities", do you mean instances or actual activities within an instance?

0 0

replied on December 19, 2016

Miruna,

These would be instances, and instances more than three days old are getting purged as if the retention in advanced Server Options was set to three days instead of 29 days.

0 0

replied on December 21, 2016

I've had them restart the Workflow and Workflow Subscriber services, but still no change. The instances are getting purged exactly as if the retention rate was set to three days. I also checked to make sure that the Workflow Admin Console was pointing to the same place after the customer just revealed to me that they had moved the Workflow database to a different SQL server.

There's no issue with database connections, else the new records would not be written, and presumably the workflows would be breaking, or not functioning at all.

I also looked directly in the Workflow database table for the server options, and it showed the same days as I had entered in the Advanced Server Options, and I checked to make sure that no one had put a shorter retention period for any of the individual workflows.

Should I be looking at a re-install of Workflow at this point?

0 0

SELECTED ANSWER

replied on December 21, 2016

No, reinstall won't change anything, the settings are in the database. I'd try running a statistics report to see if any workflows actually started in the timeframe you're looking at.

Beyond that, probably the best course of action would be to contact Tech Support with a copy of the Logs folder so we can take a closer look.

0 0

replied on December 21, 2016

Ticket submitted to support. Thanks for trying Miruna.

0 0

You are not allowed to follow up in this post.

Question

Question

Workflow is not saving completed activities more than three days old

Answer

Replies

Sign in to reply to this post.