Cleanup policies getting disabled next day after set

I have a private project at gitlab.com and try to setup cleanup policies (Settings / Packages and registries / Cleanup Policies). I set up the policy and save settings. The button text changes to “Edit cleanup rules” and I can indeed edit previously specified rules.
But next day when I get to this settings cleanup policies are again disabled. Maybe “next day” actually means “after executed”.
I found this issue: Cleanup automatic cleanup policy disabling during its execution (#262020) · Issues · GitLab.org / GitLab · GitLab.
But I’m not sure if this is exactly what I face.
What am I doing wrong?

Hi,
I have found the same problem in Gitlab CE: i create a cleanup policy in a new repository, after i while i see that the cleanup policy is being disabled automatically by Gitlab.
I don’t know if this happens because that repo doesn’t push/have docker images present in the container registry.
This is a problem because in many repo I think the cleanup policy was enabled and it wasn’t, so i had to recreate them.
Maybe some of the Gitlab Team can help us understand this behaviour? How long does it take to Gitlab to disable the policy after the creation?

@dnsmichi @stanhu

Thank you so much