# Sidebar default categories applied historically, but no change

**URL:** <https://meta.discourse.org/t/sidebar-default-categories-applied-historically-but-no-change/254067>\
**Category:** Support\
**Tags:** sidebar\
**Created:** [February 4, 2023, 5:46pm UTC](https://meta.discourse.org/t/sidebar-default-categories-applied-historically-but-no-change/254067 "2023-02-04T17:46:03Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![rahim123](https://avatars.discourse-cdn.com/v4/letter/r/df705f/32.png) [@rahim123](https://meta.discourse.org/u/rahim123)\
**Post date:** [February 4, 2023, 7:07pm UTC](https://meta.discourse.org/t/sidebar-default-categories-applied-historically-but-no-change/254067/3 "2023-02-04T19:07:42Z")

</div>

Thanks @JammyDodger for looking into it!  
Since this is an import test I wonder if the Sidekiq jobs got stopped abnormally at some point. I don’t have any jobs queued anymore.

Related?

> [@How to restart Sidekiq jobs after import](https://meta.discourse.org/t/how-to-restart-sidekiq-jobs-after-import/155133):
>
> We moved from phpBB today and as we used a bigger server for the import process we quickly created a backup in Discourse to move over to the live server. It looks like this has caused some jobs to cancel that usually run after the import (from test imports i noticed that sidekiq was busy for an hour or so after import). Is there a way to trigger the same jobs again? I do see some weirdos like an empty user list which I think is just something that needs to run the relevant job. I couldn’t find…

---

_[View the full topic](https://meta.discourse.org/t/sidebar-default-categories-applied-historically-but-no-change/254067)._