# DeepSeek-R1 randomly producing "Job exception: undefined method \`finish' for nil" error

**URL:** <https://meta.discourse.org/t/deepseek-r1-randomly-producing-job-exception-undefined-method-finish-for-nil-error/349703>\
**Category:** Bug\
**Tags:** ai, ai-bot\
**Created:** [January 30, 2025, 10:57am UTC](https://meta.discourse.org/t/deepseek-r1-randomly-producing-job-exception-undefined-method-finish-for-nil-error/349703 "2025-01-30T10:57:13Z")\
**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:** [January 31, 2025, 4:12am UTC](https://meta.discourse.org/t/deepseek-r1-randomly-producing-job-exception-undefined-method-finish-for-nil-error/349703/2 "2025-01-31T04:12:52Z")

</div>

I will put a quick bug fix into my branch, but it will probably only land some time next week

I suspect it is only a half fix, the bigger problem is that reasoning models may need ridiculous timeouts (like 5 minute timeouts) and we are now hardcoded to 60 seconds.

---

_[View the full topic](https://meta.discourse.org/t/deepseek-r1-randomly-producing-job-exception-undefined-method-finish-for-nil-error/349703)._