Retention period for workflows

Community Support
1

I have set a retention period for 5 days on my namespaces in our testing env. What else do I need to set in order to see workflows being removed? Would there be parameters I need to set in my dynamic config? Just setting the retention in admin tools doesnt really seem to be doing anything.

Thanks

2

What else do I need to set in order to see workflows being removed?

This should be it. Note it is only closed executions that would be removed from their closing time, when they pass namespace retention. Already closed execution at the time you apply your namespace retention period changes would not be updated, but still adhere to the namespace retention set at the time they closed (basically if you change retention to 5days, executions that close after the change would apply the 5 days, anything closed before would apply to whatever it was before your update/change)

Would there be parameters I need to set in my dynamic config?

one config you could change if really needed is

history.retentionTimerJitterDuration

default 30 minutes. sometimes depending on numbers of closed executions makes sense to change value (lower is small numbers of closed execs, or increase it if very large to distribute deletions of longer period of time)

Just setting the retention in admin tools doesnt really seem to be doing anything.

Not sure i fully understand this, can explain more?

3

@tihomir Appreciate the explanation here.

Not sure i fully understand this, can explain more?

Already closed execution at the time you apply your namespace retention period changes would not be updated, but still adhere to the namespace retention set at the time they closed (basically if you change retention to 5days, executions that close after the change would apply the 5 days, anything closed before would apply to whatever it was before your update/change)

Your explanation here answered my concern: When I set the retention to 5 days, I was expecting to see anything older than 5 days to be removed starting immediately. Having checked back, things are working as expected.

Thanks