Continuing the discussion from How to create a Timed Topic:
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.
Are there any errors in your logs?
Thinking this might be related?
Message (2 copies reported)
Job exception: uninitialized constant Jobs::CloseTopic
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-126.96.36.199/lib/active_support/inflector/methods.rb:263:in `block 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 <module:Sidekiq>'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/sidekiq-4.2.4/lib/sidekiq/util.rb:25:in `block in safe_thread'
That particular error has been fixed in
and it isn’t related to the current behavior that you’re seeing.
Can you see if there is a
PublishToCategory job in
Yes, there is.
in 3 days default Jobs::PublishTopicToCategory
Thanks @Vocino! I found the bug and fixed it in
In the meantime, you can cancel the job manually in
Cool, thanks for the help!