I previously reported this during beta-testing, but this still happens in 24.04, stable release.
1 Like
0c02c669c1682589f8b61ba9ce90a8b8bff97c2c fixed it in my tests, but it seems not to cover all cases. I’ll try again.
Something I realized just now is that in the “Desired retention” field, a comma is used as a decimal separator, but in the “Predicted optimal retention” field, a dot is used. In my Windows settings, a comma is used. I’m not sure if it matters in this case, but I just wanted to point it out.
I don’t think it matters in this case - we’re just showing the numbers in a different way.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.