# התנהגות משימות VersionCheck שנכשלו

**URL:** <https://meta.discourse.org/t/failed-versioncheck-jobs-behavior/211067>\
**Category:** Development\
**Created:** [4 בדצמבר,‏ 2021,‏ 12:03am UTC](https://meta.discourse.org/t/failed-versioncheck-jobs-behavior/211067 "2021-12-04T00:03:00Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Bruno\_Salazar](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bruno_salazar/32/217698_2.png) [@Bruno\_Salazar](https://meta.discourse.org/u/Bruno_Salazar)\
**Post date:** [4 בדצמבר,‏ 2021,‏ 12:03am UTC](https://meta.discourse.org/t/failed-versioncheck-jobs-behavior/211067/1 "2021-12-04T00:03:00Z")

</div>

Sorry if this is not the correct category for this.

I’m evaluating discourse and the VersionCheck Job is failling in my environment.

I’ve noticed that failed jobs are piling up inside sidekiq and probably will get moved to the “dead” section after the default 25 retries (as per [RubyDoc.info: Class: Sidekiq::JobRetry – Documentation for sidekiq (8.1.6) – RubyDoc.info](https://www.rubydoc.info/gems/sidekiq/Sidekiq/JobRetry)).

I know that I need to investigate what is causing it to fail, but the point here is: Does it make sense to maintain these jobs there? Isn’t best to simply discard failed version checks and wait the next job execution?

At this moment I have more than 80 VersionCheck jobs waiting for retry and to me it looks like a waste of resources (probably little, but still a waste)…

From what I’ve checked, adding `sidekiq_options retry: false` to [app/jobs/scheduled/version\_check.rb](https://github.com/discourse/discourse/blob/1472e47aae5bfdfb6fd9abfe89beb186c751f514/app/jobs/scheduled/version_check.rb) would solve this.

Am I missing something?

---

_[View the full topic](https://meta.discourse.org/t/failed-versioncheck-jobs-behavior/211067)._