# Email notifications not sent

**URL:** https://meta.discourse.org/t/email-notifications-not-sent/53042
**Category:** Support
**Created:** [November 17, 2016, 9:18pm UTC](https://meta.discourse.org/t/email-notifications-not-sent/53042 "2016-11-17T21:18:17Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![elutz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/elutz/32/64158_2.png) [@elutz](https://meta.discourse.org/u/elutz)
#### Post date: [November 17, 2016, 10:38pm UTC](https://meta.discourse.org/t/email-notifications-not-sent/53042/6 "2016-11-17T22:38:58Z")

</div>

You are right, 1.6.7 is the most recent: [https://github.com/discourse/discourse/releases](https://github.com/discourse/discourse/releases)  
Unfortunately the update isn’t working too, it says:

> A check for updates has not been performed lately. Ensure sidekiq is running.

This happens regularly, only after a rebuild it is some time ok. Maybe it is related to (?) :

> [@"Ensure sidekiq is running." when it is definitely running](https://meta.discourse.org/t/ensure-sidekiq-is-running-when-it-is-definitely-running/33936/19):
>
> @codinghorror @neil @sam I fixed it. Here’s what I had to do: cd /var/discourse ./launcher ssh app rails c Sidekiq.redis { |r| puts r.flushall } Then I had to exit the container and ./launcher restart app That cleared the Sidekiq Redis queue and everything started back up. If I had to guess, I upgraded Discourse when there was a backup job in the queue in Redis and somehow, upon restarting the app, the name of a class or something associated with Redis, Sidekiq, or backing up had changed, s…

---

_[View the full topic](https://meta.discourse.org/t/email-notifications-not-sent/53042)._