# Auto-close topic timer in category settings doesn't undo when moving it to another category

**URL:** <https://meta.discourse.org/t/auto-close-topic-timer-in-category-settings-doesnt-undo-when-moving-it-to-another-category/232471>\
**Category:** Feature\
**Tags:** topic-timers\
**Created:** [July 11, 2022, 8:34am UTC](https://meta.discourse.org/t/auto-close-topic-timer-in-category-settings-doesnt-undo-when-moving-it-to-another-category/232471 "2022-07-11T08:34:17Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [July 12, 2022, 6:32am UTC](https://meta.discourse.org/t/auto-close-topic-timer-in-category-settings-doesnt-undo-when-moving-it-to-another-category/232471/2 "2022-07-12T06:32:58Z")

</div>

Yeah I would say this straddles the line between feature and bug quite tightly.

For some the current behavior is desirable, for others not.

It is a bit of a can of worms cause “reason” needs to be attached to the timer, and then there are very complex edge cases to think about.

- Category A has “auto close in 20 hours”
- Category B has “auto close in 1 hour”
- Topic created in A
- 2 hours pass
- Topic recategorized to B
- What should happen?
- Topic recategorized to A
- What should happen?

I kind of think the current “decision only applies to creation time” is the only easy way to reason about things.

---

_[View the full topic](https://meta.discourse.org/t/auto-close-topic-timer-in-category-settings-doesnt-undo-when-moving-it-to-another-category/232471)._
