# 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:** 6

<div class="post-metadata">

**Author:** ![fearlessfrog](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fearlessfrog/32/119653_2.png) [@fearlessfrog](https://meta.discourse.org/u/fearlessfrog)\
**Post date:** [16.Январь.2019 19:27:23 UTC](https://meta.discourse.org/t/image-lightbox-stopped-appearing-on-beta-8-update/106624/6 "2019-01-16T19:27:23Z")

</div>

If it helps anyone else, we’ve found that for our hardware of a dual proc DigitalOcean with 4GB seems to fall behind with a default ‘rebake old posts’ set to 80. We’ve been going for a few years and have a lot of image intensive posts, so YMMV.

Our sidekiq was clear of PostProcess jobs about 12 hours ago, but it’s crept up to about 4,500 enqueued again this morning, causing delays in new post processing.

I’ve set the rebake\_old\_posts\_count value to ‘20’ and it seems to be slowly making headway now. The setting can be found via admin here:

```
 admin/site_settings/category/all_results?filter=rebake%20old

```

@sam even though this is an unusual rebake, being especially CPU intensive (and I imagine some S3 back/forth as well), is there a way that this rebake value could be backed off if sidekiq is backlogged so much? I’m not meaning anything too complex an algorithm, just something that could automatically half it if the system is increasingly getting behind?

---

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