Rudder

There was significant code changes between 4.1 and 4.3 and I'm not at all confident about doing any changes in 4.1 in that part - even in 4.3, it may not be trivial.

So, the code is not that simple to change. It need more work than thought, evec in 4.3.
The reason is that we only have one scheduler for that, and that that TTL would need to live in an other to go below day atomicity. That means an other display, etc.
But it also need code to deal differently with the "0" case, because for that one, we want 0 to mean "don't log at all", not "don't clean at all".
So actually, we need 0 to do a "truncate" or similar if table non-empty, but ALSO to have a check in report processing which don't log at all nodecompliance in that case.

So... All that is needs a couple of days to be taken care of in a released version.

It may have already been done in 5.0.12, retargeting to 5.0 and asking people who knows!!

compliance has its own ttl now