# Rebaking posts does not fix broken locally downloaded linked images

**URL:** <https://meta.discourse.org/t/rebaking-posts-does-not-fix-broken-locally-downloaded-linked-images/98470>\
**Category:** Support\
**Created:** [10월 1, 2018, 12:37오후 UTC](https://meta.discourse.org/t/rebaking-posts-does-not-fix-broken-locally-downloaded-linked-images/98470 "2018-10-01T12:37:13Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![vinothkannans](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vinothkannans/32/86465_2.png) [@vinothkannans](https://meta.discourse.org/u/vinothkannans)\
**Post date:** [10월 2, 2018, 2:09오전 UTC](https://meta.discourse.org/t/rebaking-posts-does-not-fix-broken-locally-downloaded-linked-images/98470/3 "2018-10-02T02:09:29Z")

</div>

I agree, rebake should retry to download all broken images.

> [@sam](#):
>
> hard caching image is broken forever is a bit too strict here, at a minimum we should expire that information after N days.

I think it’s not needed after we implemented the both “retry on rebake” and “[retry broken images N times in X hours](https://meta.discourse.org/t/image-downloader-should-be-more-resilient-to-download-failures/94883/12)” features. We can extend the X hours to 1, 10, 24, 72, 168.

---

_[View the full topic](https://meta.discourse.org/t/rebaking-posts-does-not-fix-broken-locally-downloaded-linked-images/98470)._
