The mysterious case of the disappearing workflows

Uncle Rob · ‎12-05-2016

I have a custom task type that generates a workflow. In a 3 year old solution, about once a year, a bunch of tasks appear to lose their workflow context.

So two questions:

1) Has anyone experienced either spontaneous droppage of a WF context *OR* a WF context not created for a record that so obviously me the criteria?

2) Is there any way to report on tasks that do not have a workflow context?

oharel · ‎12-09-2016

I had a similar issue and contacted HI (running Eureka). They said:

"There is an OOB Table Clean-up job set-up for all workflow context older than 180 days. This will delete all finished or ended workflow context in your instance if the context has ended after around 15M seconds or 180 days.

From Fuji version we have disabled this table clean-up job out-of-the-box."

harel

View solution in original post

Uncle Rob · ‎12-05-2016

Just took a peek at this thread: Workflow context expiration?

Workflows don't expire or in any way "go away" after completion do they?

Community Alums · ‎12-05-2016

I think there may be a maximum runtime. Check the system properties for workflows in your instance.

Uncle Rob · ‎12-05-2016

But is runtime the amount of time it can stay active? Or the amount of time it exists at all?

Community Alums · ‎12-05-2016

I looked, and the system property I recalled didn't do what I thought it did. I would maybe look at scheduled jobs and see if there's one that kills long-running workflows. Beyond that, I don't really have any idea what could be doing that.