# How to avoid potential issues when rebaking all posts? **URL:** \ **Category:** Support\ **Tags:** onebox\ **Created:** [December 18, 2022, 12:58pm UTC](https://meta.discourse.org/t/how-to-avoid-potential-issues-when-rebaking-all-posts/249271 "2022-12-18T12:58:28Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)\ **Post date:** [December 20, 2022, 11:48am UTC](https://meta.discourse.org/t/how-to-avoid-potential-issues-when-rebaking-all-posts/249271/2 "2022-12-20T11:48:59Z")
> [@What rebake is required for the new autocomplete styling?](https://meta.discourse.org/t/what-rebake-is-required-for-the-new-autocomplete-styling/249642/6): > > Is there a pattern perhaps we could use to rebake all posts except the ones with an embed/onebox? > > > [@](#): > > > > Want to rebake all the posts matching a string or regular expression? Let’s do it! Access Your Site First connect to your Droplet via SSH, and enter the Docker container for your Discourse instances: cd /var/discourse ./launcher enter app Rebake All Posts Containing a Specific String Run this command: rake posts:rebake\_match[“pattern”] Replace pattern with the string you want to match. Note that the match performed will be case insensitive. rake posts:rebake\_match[“slight\_smile”] The … It feels to me that we need an enhancement to rebake, to be more careful - rate limit on selected sites or perhaps on all sites - inherit the original onebox if the refetch fails for any reason In other words, I think we need a non-damaging rebake, at least as a selectable option. (There will be some discourse communities who value an up to date 404, or who don’t value old posts at all, but there will also be communities which very much want to preserve old threads intact.) --- _[View the full topic](https://meta.discourse.org/t/how-to-avoid-potential-issues-when-rebaking-all-posts/249271)._