Now the troubling part: I don’t see it in every topic. Some are correct some are not. Also some topics created after the update show the error (so it is probably not due to migration).
Fortunately it only displays that it will close in few seconds, in reality topics are closed on correct schedule (e.g. 6 months)
Hmm that is interesting that it fixes itself when you open the modal. I will have a look into this. Also, I have a PR open to introduce a new duration component; I am glad you opened this issue because now I can also replace this:
I’ve done some more investigation (still on f6e6ae5e24) and found that only old topics exhibit this strange behaviour so the migration bug probably will be the case after all…
Old buggy timers have duration = 4320 and duration_minutes = NULL.
New ones working well have duration = NULL and duration_minutes = 259200