# Sidekiq Heartbeat-Test fehlgeschlagen in Build 3.6.0 Beta 2

**URL:** <https://meta.discourse.org/t/sidekiq-heartbeat-test-failed-in-build-3-6-0-beta-2/385945>\
**Category:** Product Support\
**Created:** [16. Oktober 2025 um 22:15 UTC](https://meta.discourse.org/t/sidekiq-heartbeat-test-failed-in-build-3-6-0-beta-2/385945 "2025-10-16T22:15:05Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![RBoy](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@RBoy](https://meta.discourse.org/u/RBoy)\
**Post date:** [29. Oktober 2025 um 21:47 UTC](https://meta.discourse.org/t/sidekiq-heartbeat-test-failed-in-build-3-6-0-beta-2/385945/7 "2025-10-29T21:47:02Z")

</div>

Ok. Zu Ihrer Information, es sieht so aus, als ob dies in einer neueren Version von Sidekiq behoben werden soll, aber ich bin mir nicht sicher, ob Discourse Änderungen vornehmen muss, um diese Korrektur in seine APIs zu integrieren.

> <https://github.com/mhenrixon/sidekiq-unique-jobs/pull/815>
>
> According to \[Sidekiq 7.2 changelog\](https://github.com/sidekiq/sidekiq/blob/mai…n/Changes.md#720), using \`byscore: true\` and \`nx: true\` will now throw, which causes Sidekiq not to start up anymore when using \`sidekiq-unique-jobs\`

---

_[View the full topic](https://meta.discourse.org/t/sidekiq-heartbeat-test-failed-in-build-3-6-0-beta-2/385945)._