# 1.8M PullHotLinkedImages in our sidekiq backlog

**URL:** <https://meta.discourse.org/t/1-8m-pullhotlinkedimages-in-our-sidekiq-backlog/36589>\
**Category:** Product Support\
**Created:** [Dezembro 11, 2015, 8:37pm UTC](https://meta.discourse.org/t/1-8m-pullhotlinkedimages-in-our-sidekiq-backlog/36589 "2015-12-11T20:37:21Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Paulo\_Silveira](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/paulo_silveira/32/121689_2.png) [@Paulo\_Silveira](https://meta.discourse.org/u/Paulo_Silveira)\
**Post date:** [Dezembro 11, 2015, 8:37pm UTC](https://meta.discourse.org/t/1-8m-pullhotlinkedimages-in-our-sidekiq-backlog/36589/1 "2015-12-11T20:37:21Z")

</div>

We are trying to cope with a huge batch of PullHotLinkedImages (and ProcessoPost/UpdateGravatar/CrawlLink) in our sidekiq queue after migrating our forum. And as the posts are being processed, the queue is getting even bigger!

To be honest, I dont even understand why we have so many PullHotLinkedImages/etc, since our posts have almost no images attached. Could/should we just remove all these jobs?

 ![](https://global.discourse-cdn.com/meta/original/3X/6/1/6123e8262ee9ea8fc3163f5e4e56609834969c53.png)

Any hints?

---

_[View the full topic](https://meta.discourse.org/t/1-8m-pullhotlinkedimages-in-our-sidekiq-backlog/36589)._