running sidekiq job in console

working with clients database locally has to be done without having sidekiq running to prevent side-effects like causing relay-interactins, mail-sends and others. but. sometimes, to debug burried mantraps you have to use the local connsole and you like to execute a task, which is usually performed by sidekiq. there is a _simple_ way to run those tasks locally.

asuming that you have one item in your queue to execute, you can _easy_ run:

```ruby
job = Sidekiq::Queue.new("low").first
job.klass.constantize.new.perform(*job.args)
```

if you have to find something by the id shown in backend, you can utilize the [Sidekiq API](https://github.com/mperham/sidekiq/wiki/API) for distinct access.

marcotralles
August 28, 2020