RBoy reports a recurring error appearing in logs after upgrading to Discourse 2026.9.0: 'hijack discourse_ai/embeddings/embeddings search' is still running after 90 seconds on db default, accompanied by a backtrace pointing to the scheduler and message bus timer thread.
sam asks how embeddings are configured and what overall performance looks like. RBoy confirms it’s a standard out-of-the-box Gemini embedding setup configured years ago, untouched since, and this is the first embeddings-related error encountered.
Raj_Discourse_expert notes the config looks standard and asks whether HyDE is enabled and whether PostgreSQL logs or active queries can be captured when the warning triggers, suggesting a possible regression or slow database query introduced in 2026.9.0.
RBoy confirms HyDE has been enabled for a long time and asks where to retrieve the requested logs. Later, RBoy reports the error has recurred (now 4 copies), and offers to share further diagnostics or provide direct access via PM for deeper debugging.
I’m seeing this new error in the logs are upgrading to 2026.9.0
Message (2 copies reported)
'hijack discourse_ai/embeddings/embeddings search ' is still running after 90 seconds on db default, this process may need to be restarted!
Backtrace
/var/www/discourse/vendor/bundle/ruby/3.4.0/gems/activesupport-8.1.3.1/lib/active_support/broadcast_logger.rb:218:in 'block in ActiveSupport::BroadcastLogger#dispatch'
/var/www/discourse/vendor/bundle/ruby/3.4.0/gems/activesupport-8.1.3.1/lib/active_support/broadcast_logger.rb:217:in 'Array#map'
/var/www/discourse/vendor/bundle/ruby/3.4.0/gems/activesupport-8.1.3.1/lib/active_support/broadcast_logger.rb:217:in 'ActiveSupport::BroadcastLogger#dispatch'
/var/www/discourse/vendor/bundle/ruby/3.4.0/gems/activesupport-8.1.3.1/lib/active_support/broadcast_logger.rb:129:in 'ActiveSupport::BroadcastLogger#error'
/var/www/discourse/lib/scheduler/defer.rb:133:in 'block (2 levels) in Scheduler::Deferrable#do_work'
/var/www/discourse/vendor/bundle/ruby/3.4.0/gems/message_bus-5.0.0/lib/message_bus/timer_thread.rb:117:in 'MessageBus::TimerThread#do_work'
/var/www/discourse/vendor/bundle/ruby/3.4.0/gems/message_bus-5.0.0/lib/message_bus/timer_thread.rb:95:in 'block (2 levels) in MessageBus::TimerThread#queue'
This is the config, standard OOB gemini embedding. Configured it years ago and haven’t touched it since. This is the first time I’m seeing any error related to embeddings. Anything specific you need from the setup?
@RBoy Thanks, the configuration looks standard. Could you confirm whether HyDE is enabled and share PostgreSQL logs or active queries when the warning occurs? Since this started after upgrading to 2026.9.0, it may be a regression or a slow database query.
Yes HyDE is enabled (and has been as far back as I can remember). Let me know where to get you the logs from. I just looked at the discourse error logs, noticed this and reported it.
Message (4 copies reported)
'hijack discourse_ai/embeddings/embeddings search ' is still running after 90 seconds on db default, this process may need to be restarted!
Backtrace
/var/www/discourse/vendor/bundle/ruby/3.4.0/gems/activesupport-8.1.3.1/lib/active_support/broadcast_logger.rb:218:in 'block in ActiveSupport::BroadcastLogger#dispatch'
/var/www/discourse/vendor/bundle/ruby/3.4.0/gems/activesupport-8.1.3.1/lib/active_support/broadcast_logger.rb:217:in 'Array#map'
/var/www/discourse/vendor/bundle/ruby/3.4.0/gems/activesupport-8.1.3.1/lib/active_support/broadcast_logger.rb:217:in 'ActiveSupport::BroadcastLogger#dispatch'
/var/www/discourse/vendor/bundle/ruby/3.4.0/gems/activesupport-8.1.3.1/lib/active_support/broadcast_logger.rb:129:in 'ActiveSupport::BroadcastLogger#error'
/var/www/discourse/lib/scheduler/defer.rb:133:in 'block (2 levels) in Scheduler::Deferrable#do_work'
/var/www/discourse/vendor/bundle/ruby/3.4.0/gems/message_bus-5.0.0/lib/message_bus/timer_thread.rb:117:in 'MessageBus::TimerThread#do_work'
/var/www/discourse/vendor/bundle/ruby/3.4.0/gems/message_bus-5.0.0/lib/message_bus/timer_thread.rb:95:in 'block (2 levels) in MessageBus::TimerThread#queue'
Let me know what I can get you to debug this further and from where. Feel free to PM to discuss it further if you need direct access.
