# Image lightbox stopped appearing on beta 8 update

**URL:** <https://meta.discourse.org/t/image-lightbox-stopped-appearing-on-beta-8-update/106624>\
**Category:** Product Support\
**Created:** [15.Январь.2019 20:32:08 UTC](https://meta.discourse.org/t/image-lightbox-stopped-appearing-on-beta-8-update/106624 "2019-01-15T20:32:08Z")\
**Posts on this page:** 1\
**Showing post:** 15

<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:** [17.Январь.2019 02:08:11 UTC](https://meta.discourse.org/t/image-lightbox-stopped-appearing-on-beta-8-update/106624/15 "2019-01-17T02:08:11Z")

</div>

> [@codinghorror](#):
>
> Why can’t _new_ posts jump the queue here, so they get processed first? It seems odd that background image rebuilds of old posts would pre-empt a new post someone just made.

At the moment the rebake happens in the “low priority” queue. New posts happen in the “normal” queue.

However, if we can not keep up we can starve the “low” queue, it includes the jobs “notify mailing list”, “pull hotlinked images”, “create avatar thumbnails”, “anonymize user”, “send user emails”, “update username for username renames”

We can introduce a “super low priority” queue purely for rebakes, but it seems rather complicated to me.

---

_[View the full topic](https://meta.discourse.org/t/image-lightbox-stopped-appearing-on-beta-8-update/106624)._
