Why does the AI model stop responding

Product Support

AI-generated summary

The discussion revolves around an AI model, Quen QwQ-32B, stopping responses in the composer, with the blue light ceasing to blink. BrianC notes the issue occurs during long reasoning processes, not reaching the 6-minute timeout. The logs reveal an error: Discourse::InvalidParameters : persona_id in LlmPersonaTriage.handle, suggesting a missing or deleted persona linked to automation. Sam confirms the timeout was increased to 6 minutes, but acknowledges potential edge cases. BrianC clarifies that he deleted personas, possibly causing the issue, and asks if the timeout applies to self-hosted setups. Sam confirms the timeout exists but hints at unresolved edge cases.

1

Hi,
I am using Quen QwQ-32B which for my purposes responds well albeit with significant slow reasoning. When using the model at times in the composer the model stops responding and the blue light stops blinking. I thought this may be a timeout issue but not sure. Sam indicated in this post that the timeout was increased to 6 minutes.

https://meta.discourse.org/t/deepseek-r1-randomly-producing-job-exception-undefined-method-finish-for-nil-error/349703/3?u=brianc
The thinking is long but no where near 6 minutes, maybe 2 or so.

These are the messages from the logs. Any ideas what the issue may be. Not sure what InvalidParmeters: persona_id is about. Maybe this is causing the failure.

Any insights will be appreciated!

Error responding to: /t/group-study-setup-participants-passage-focus/1254/3 in LlmPersonaTriage.handle : Discourse::InvalidParameters : persona_id

/var/www/discourse/plugins/discourse-ai/lib/automation/llm_persona_triage.rb:6:in handle' /var/www/discourse/plugins/discourse-ai/discourse_automation/llm_persona_triage.rb:40:in block (2 levels) in ’
/var/www/discourse/plugins/automation/app/models/discourse_automation/automation.rb:141:in trigger!' /var/www/discourse/plugins/automation/app/jobs/regular/discourse_automation/trigger.rb:29:in execute’
/var/www/discourse/app/jobs/base.rb:316:in block (2 levels) in perform' rails_multisite-6.1.0/lib/rails_multisite/connection_management/null_instance.rb:49:in with_connection’
rails_multisite-6.1.0/lib/rails_multisite/connection_management.rb:21:in with_connection' /var/www/discourse/app/jobs/base.rb:303:in block in perform’
/var/www/discourse/app/jobs/base.rb:299:in each' /var/www/discourse/app/jobs/base.rb:299:in perform’
sidekiq-7.3.9/lib/sidekiq/processor.rb:220:in execute_job' sidekiq-7.3.9/lib/sidekiq/processor.rb:185:in block (4 levels) in process’
sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:180:in traverse' sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:183:in block in traverse’
/var/www/discourse/lib/sidekiq/pausable.rb:132:in call' sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:182:in traverse’
sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:183:in block in traverse' sidekiq-7.3.9/lib/sidekiq/job/interrupt_handler.rb:9:in call’
sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:182:in traverse' sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:183:in block in traverse’
sidekiq-7.3.9/lib/sidekiq/metrics/tracking.rb:26:in track' sidekiq-7.3.9/lib/sidekiq/metrics/tracking.rb:134:in call’
sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:182:in traverse' sidekiq-7.3.9/lib/sidekiq/middleware/chain.rb:173:in invoke’
sidekiq-7.3.9/lib/sidekiq/processor.rb:184:in block (3 levels) in process' sidekiq-7.3.9/lib/sidekiq/processor.rb:145:in block (6 levels) in dispatch’
sidekiq-7.3.9/lib/sidekiq/job_retry.rb:118:in local' sidekiq-7.3.9/lib/sidekiq/processor.rb:144:in block (5 levels) in dispatch’
sidekiq-7.3.9/lib/sidekiq/config.rb:39:in block in <class:Config>' sidekiq-7.3.9/lib/sidekiq/processor.rb:139:in block (4 levels) in dispatch’
sidekiq-7.3.9/lib/sidekiq/processor.rb:281:in stats' sidekiq-7.3.9/lib/sidekiq/processor.rb:134:in block (3 levels) in dispatch’
sidekiq-7.3.9/lib/sidekiq/job_logger.rb:15:in call' sidekiq-7.3.9/lib/sidekiq/processor.rb:133:in block (2 levels) in dispatch’
sidekiq-7.3.9/lib/sidekiq/job_retry.rb:85:in global' sidekiq-7.3.9/lib/sidekiq/processor.rb:132:in block in dispatch’
sidekiq-7.3.9/lib/sidekiq/job_logger.rb:40:in prepare' sidekiq-7.3.9/lib/sidekiq/processor.rb:131:in dispatch’
sidekiq-7.3.9/lib/sidekiq/processor.rb:183:in block (2 levels) in process' sidekiq-7.3.9/lib/sidekiq/processor.rb:182:in handle_interrupt’
sidekiq-7.3.9/lib/sidekiq/processor.rb:182:in block in process' sidekiq-7.3.9/lib/sidekiq/processor.rb:181:in handle_interrupt’
sidekiq-7.3.9/lib/sidekiq/processor.rb:181:in process' sidekiq-7.3.9/lib/sidekiq/processor.rb:86:in process_one’
sidekiq-7.3.9/lib/sidekiq/processor.rb:76:in run' sidekiq-7.3.9/lib/sidekiq/component.rb:10:in watchdog’
sidekiq-7.3.9/lib/sidekiq/component.rb:19:in `block in safe_thread’ ht to search.

3

Are you sure those are the only errors, the error indicates you configured triage with a persona and then deleted

4

Thanks Sam, those are the only errors from /logs. I have been messing around with Triage and have deleted personas for sure. I will look in automations and see if any have no model.

Do you think this would be related to the AI issue stopping responding? Is the 6 minute timeout increased for self hosted or only Meta Discourse?

5

6 minute timeout is indeed there, but I also saw timeouts on some models with some tests, so there could be some edge cases lurking