# Don't use sidekiq queue to process "problems have been found" email

**URL:** <https://meta.discourse.org/t/dont-use-sidekiq-queue-to-process-problems-have-been-found-email/91867>\
**Category:** Feature\
**Created:** [July 9, 2018, 9:55am UTC](https://meta.discourse.org/t/dont-use-sidekiq-queue-to-process-problems-have-been-found-email/91867 "2018-07-09T09:55:22Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![LeoMcA](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/leomca/32/87233_2.png) [@LeoMcA](https://meta.discourse.org/u/LeoMcA)\
**Post date:** [July 9, 2018, 10:03am UTC](https://meta.discourse.org/t/dont-use-sidekiq-queue-to-process-problems-have-been-found-email/91867/3 "2018-07-09T10:03:03Z")

</div>

It hasn’t been for us - which may point to it being another problem - we’ve been having to restart our containers to bring it back up. We’re still investigating.

I think this feature request stands alone, however. Taking as many things as possible that might go wrong out of the path from problem to alert seems like a good idea to me.

---

_[View the full topic](https://meta.discourse.org/t/dont-use-sidekiq-queue-to-process-problems-have-been-found-email/91867)._