# Topic timer does not accept values \<1 hour

**URL:** <https://meta.discourse.org/t/topic-timer-does-not-accept-values-1-hour/164121>\
**Category:** Bug\
**Tags:** topic-timers\
**Created:** [September 15, 2020, 5:57pm UTC](https://meta.discourse.org/t/topic-timer-does-not-accept-values-1-hour/164121 "2020-09-15T17:57:51Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ljpp](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ljpp/32/96506_2.png) [@ljpp](https://meta.discourse.org/u/ljpp)\
**Post date:** [September 15, 2020, 5:57pm UTC](https://meta.discourse.org/t/topic-timer-does-not-accept-values-1-hour/164121/1 "2020-09-15T17:57:51Z")

</div>

Stable channel, shallow bug.

Topic time does not accept values less than 1 hour. Has worked before, for a very long time.

- Auto-close topic
- Close based on last post
- Try to set a value below 1 hour, say 0.25 for 15 minutes

One hour is a very long time for a heated discussion. We actively use values around 10 minutes to end our game chats. It works very well as the timer triggers when things start to cool down (our game topics get up to 1000 posts in a couple of hours).

Propose the fix to be backported to the stable channel. Reasoning: Old basic functionality broken.

---

<div class="post-metadata">

**Author:** ![ljpp](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ljpp/32/96506_2.png) [@ljpp](https://meta.discourse.org/u/ljpp)\
**Post date:** [October 21, 2020, 8:20am UTC](https://meta.discourse.org/t/topic-timer-does-not-accept-values-1-hour/164121/2 "2020-10-21T08:20:15Z")

</div>

Reproduced with 2.6.0 beta4.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [October 22, 2020, 9:43pm UTC](https://meta.discourse.org/t/topic-timer-does-not-accept-values-1-hour/164121/3 "2020-10-22T21:43:47Z")

</div>

@martin is planning to revamp this dialog entirely in the next version of Discourse so we will probably deal with it then.

(I was hoping it would make this release but probably not)

---

<div class="post-metadata">

**Author:** ![ljpp](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ljpp/32/96506_2.png) [@ljpp](https://meta.discourse.org/u/ljpp)\
**Post date:** [February 10, 2021, 7:20pm UTC](https://meta.discourse.org/t/topic-timer-does-not-accept-values-1-hour/164121/5 "2021-02-10T19:20:58Z")

</div>

Just verified this in production (CDCK’s SaaS Discourse). Value of 0.1 hours was accepted (6 minutes) and topic closed accordingly.

---

<div class="post-metadata">

**Author:** ![martin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/martin/32/491371_2.png) [@martin](https://meta.discourse.org/u/martin)\
**Post date:** [February 10, 2021, 10:32pm UTC](https://meta.discourse.org/t/topic-timer-does-not-accept-values-1-hour/164121/6 "2021-02-10T22:32:10Z")

</div>

I am glad you found this yourself, I had a reminder set to post an update here 🙂

---

<div class="post-metadata">

**Author:** ![martin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/martin/32/491371_2.png) [@martin](https://meta.discourse.org/u/martin)\
**Post date:** [February 10, 2021, 10:32pm UTC](https://meta.discourse.org/t/topic-timer-does-not-accept-values-1-hour/164121/7 "2021-02-10T22:32:12Z")

</div>


