# Timed topic's date posted keeps moving
**URL:** https://meta.discourse.org/t/timed-topics-date-posted-keeps-moving/60737
**Category:** Bug
**Created:** [10 Aprile 2017, 7:36pm UTC](https://meta.discourse.org/t/timed-topics-date-posted-keeps-moving/60737 "2017-04-10T19:36:29Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Vocino](https://meta.discourse.org/u/Vocino)
#### Post date: [10 Aprile 2017, 7:36pm UTC](https://meta.discourse.org/t/timed-topics-date-posted-keeps-moving/60737/1 "2017-04-10T19:36:29Z")
Continuing the discussion from [How to create a Timed Topic](https://meta.discourse.org/t/how-to-create-a-timed-topic/60731):
I’m noticing a strange bug where a topic I posted in a private category on Friday, to be timed for posting to a public category on Saturday, is now being continuously moved to the top of the latest topics.
The timestamp on it reads “13m” right now and will reset routinely. I’m not sure how often yet as I just noticed this. I’m assuming it’s being triggered possibly every time the clock reaches the hour it was set to or something along those lines.
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [11 Aprile 2017, 1:41am UTC](https://meta.discourse.org/t/timed-topics-date-posted-keeps-moving/60737/3 "2017-04-11T01:41:20Z")
Are there any errors in your logs?
---
### Author:  [@Vocino](https://meta.discourse.org/u/Vocino)
#### Post date: [11 Aprile 2017, 2:09am UTC](https://meta.discourse.org/t/timed-topics-date-posted-keeps-moving/60737/4 "2017-04-11T02:09:40Z")
Thinking this might be related?
```plaintext
Recent
Message (2 copies reported)
Job exception: uninitialized constant Jobs::CloseTopic
Backtrace
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/inflector/methods.rb:263:in `const_get'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/inflector/methods.rb:263:in `block in constantize'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/inflector/methods.rb:259:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/inflector/methods.rb:259:in `inject'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/inflector/methods.rb:259:in `constantize'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/core_ext/string/inflections.rb:66:in `constantize'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sidekiq-4.2.4/lib/sidekiq/processor.rb:126:in `block in process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sidekiq-4.2.4/lib/sidekiq.rb:35:in `block in '
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sidekiq-4.2.4/lib/sidekiq/processor.rb:124:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sidekiq-4.2.4/lib/sidekiq/processor.rb:81:in `process_one'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sidekiq-4.2.4/lib/sidekiq/processor.rb:69:in `run'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sidekiq-4.2.4/lib/sidekiq/util.rb:17:in `watchdog'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sidekiq-4.2.4/lib/sidekiq/util.rb:25:in `block in safe_thread'
```
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [11 Aprile 2017, 2:22am UTC](https://meta.discourse.org/t/timed-topics-date-posted-keeps-moving/60737/5 "2017-04-11T02:22:25Z")
That particular error has been fixed in
[https://github.com/discourse/discourse/commit/e8eaffbd724e8618bfb58b6f0fba88bae4c8ee1b](https://github.com/discourse/discourse/commit/e8eaffbd724e8618bfb58b6f0fba88bae4c8ee1b)
and it isn’t related to the current behavior that you’re seeing.
Can you see if there is a `PublishToCategory` job in `https:///sidekiq/scheduled`?
---
### Author:  [@Vocino](https://meta.discourse.org/u/Vocino)
#### Post date: [11 Aprile 2017, 2:25am UTC](https://meta.discourse.org/t/timed-topics-date-posted-keeps-moving/60737/6 "2017-04-11T02:25:41Z")
Yes, there is.
```plaintext
in 3 days default Jobs::PublishTopicToCategory
{"topic_status_update_id"=>868, "current_site_id"=>"default"}
```
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [11 Aprile 2017, 2:34am UTC](https://meta.discourse.org/t/timed-topics-date-posted-keeps-moving/60737/7 "2017-04-11T02:34:25Z")
Thanks @Vocino! I found the bug and fixed it in
[https://github.com/discourse/discourse/commit/aadf4805a539425021dff8352cc4aa404c4159f0](https://github.com/discourse/discourse/commit/aadf4805a539425021dff8352cc4aa404c4159f0)
In the meantime, you can cancel the job manually in `https:///sidekiq/scheduled`.
---
### Author:  [@Vocino](https://meta.discourse.org/u/Vocino)
#### Post date: [11 Aprile 2017, 2:36am UTC](https://meta.discourse.org/t/timed-topics-date-posted-keeps-moving/60737/8 "2017-04-11T02:36:22Z")
Cool, thanks for the help!
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [12 Aprile 2017, 8:43am UTC](https://meta.discourse.org/t/timed-topics-date-posted-keeps-moving/60737/9 "2017-04-12T08:43:18Z")