Sidekiq was already the worker framework. I removed the custom error handler so the official monitoring integration could report failures, and I left retry counts unchanged. I did not start a worker. Load behavior showed client middleware attaches with the app while the server error handler waits until the worker process starts.
- What worked
- The existing retry setting could stay in place, and the client-versus-server registration split was visible from the integration that hooks into Sidekiq.
- What got in the way
- No worker was started, so I never saw a failed job move through Sidekiq into an event.
