### Summary This is not not an issue until we upgrade to Sidekiq 7.0 Multiple jobs are generating the warning: ``` Job arguments to <workername> do not serialize to JSON safely. This will raise an error in Sidekiq 7.0. See https://github.com/mperham/sidekiq/wiki/Best-Practices or raise an error today by calling `Sidekiq.strict_args!` during Sidekiq initialization. ``` There's a couple of existing issues for specific jobs, and multiple reports from customers for different workers. - https://gitlab.com/gitlab-org/gitlab/-/issues/353911+ - https://gitlab.com/gitlab-org/gitlab/-/issues/351870#note_1177260181 As each worker will require effort by different teams, I'll open a bunch of issues for those teams and relate them all to this issue. ### Example Project <!-- If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version. --> ### Relevant logs and/or screenshots https://log.gprd.gitlab.net/goto/800d7080-6820-11ed-85ed-e7557b0a598c <!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise. --> GitLab Enterprise Edition 15.6.0-pre gitlab@3d55ac97c8de0cd2cc59aaff50e27c7632cc92bc ### Possible fixes One worker got fixed in %"15.1" - https://gitlab.com/gitlab-org/gitlab/-/merge_requests/89736+ From the [issue](https://gitlab.com/gitlab-org/gitlab/-/issues/351870): > It's sufficient to ensure that the hash data uses string keys. <!-- If you can, link to the line of code that might be responsible for the problem. -->