# Webhooks/Sidekiq issue on dev instance

**URL:** https://meta.discourse.org/t/webhooks-sidekiq-issue-on-dev-instance/71129
**Category:** Development
**Created:** [1 Ottobre 2017, 2:07pm UTC](https://meta.discourse.org/t/webhooks-sidekiq-issue-on-dev-instance/71129 "2017-10-01T14:07:29Z")
**Posts on this page:** 1
**Showing post:** 10

<div class="post-metadata">

### Author: ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [2 Ottobre 2017, 10:19pm UTC](https://meta.discourse.org/t/webhooks-sidekiq-issue-on-dev-instance/71129/10 "2017-10-02T22:19:41Z")

</div>

Stuck jobs in development mode are a known problem with Sidekiq and Rails 5.1  
It’s probably because of missing dependencies. See the following post for more information on that.

> [@When should Discourse upgrade to Rails 5?](https://meta.discourse.org/t/when-should-discourse-upgrade-to-rails-5/67123/26):
>
> Rails 5.1 is merged into Discourse. One notable change which was a source of pain in development for me is that Sidekiq supports live reloading with Rails 5 but dependencies in each file has to be required properly. Otherwise, the job will be stucked in the Sidekiq queue. I’ve fixed most that I can find but if you run into any other job, feel free to let me know.

Feel free to send a pull request if you find missing dependencies in sidekiq jobs.

Unfortunately the `ProcessPost` job can’t be fixed that way. We are aware of the problem…  
As a workaround you can change `config.eager_load` to `true` in `development.rb`

---

_[View the full topic](https://meta.discourse.org/t/webhooks-sidekiq-issue-on-dev-instance/71129)._