The mysterious case of the disappearing workflows

[Uncle Rob]

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?

[Michael Fry1]

Seems like a good thing unless something replaced it?

[Uncle Rob]

Its only a good thing if you are 100% positive 100% of the time that you have 0 use cases where a ticket is legitimately updated long after its workflow has been completed.

Essentially, the rule assumes:

1)   That ticket life cycle = workflow life cycle

2)   That old = bad

[oharel · Accepted solution]

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

[Uncle Rob]

Yep, that's exactly what I got (minus the specific version).

That's a hella dangerous time bomb though.   Wowzers.