There is an issue with the autoclose topic feature in Discourse, where setting it to 1 minute results in the topic actually closing after 2 minutes. geoff777 and SaraDev reported this issue, with SaraDev confirming it on Discourse Version 2.9.0.beta2. However, maiki found that the issue was fixed in 2.9.0.beta3, with the topic closing exactly 1 minute after the autoclose timer was set. geoff777 later confirmed that the issue was fixed, but noted that there may be a slight delay (26 seconds in his case) between the countdown ending and the topic actually closing, likely due to background tasks and system load.
If you set autoclose topic in Category settings to 1 minute.
The topic countdown to closure text output is correct but you get an extra minute where the topic is still open for replies.
I was able to reply between 1-2 minutes when the topic should have already closed after 1 minute.
The topic closed after 2 minutes … see below.
A topic with a category where the Auto-close is set to 1 minute doesn’t get closed until after 2 minutes. The system displays the following message after the topic is successfully closed - “This topic was automatically closed after 2 minutes. New replies are no longer allowed.”
1 minute auto-closing is working as expected for me, with the caveat that I’m using a sandbox with no other activity. Also using 2.9.0.beta3, so maybe this was fixed.
When I set the auto-close topic timer to 1 minute, I get the following message immediately upon publishing:
The text has changed. It now says 1 minute. So it looks like it has been fixed.
I tested and the countdown is exactly 1 minute. Then the dialogue disappeared and the topic stayed open with a reply button for 26 seconds. Then the topic closed. I guess that is unavoidable and is due to the system doing background tasks while closing the topic and is going to vary depending on load etc.
