I did experience a problem with a Sidekiq backed job, which had named (not positional) parameters. The job would be called seemingly w/o parameters. I did change the signature of the perform method and got around it. Perhaps I should open another issue?
From @psteininger (https://github.com/nickelser/activejob-traffic_control/issues/3):