The origin of the problem is that the client middleware is triggered when you do `Worker.perform_at`. That makes a pending status entry at 0% appear and keep that way until the job runs in the future. In our case that might mean a month long status at 0%.

When the job actually runs, your wrapper on `perform` triggers the container load ([here](https://github.com/cryo28/sidekiq_status/blob/master/lib/sidekiq_status/worker.rb#L18)) and that somehow makes `Container` creates the status data when `load` is called.

I'm sure it works.