Issue Description

Our project relies on an AWS Lambda pushing Sidekiq::Jobs as "raw" messages in Redis for Sidekiq worker to pick up.

The lambda is not aware of the application business logic (eg: which job is retryable or not) meaning it does not push "retry" in the message payload.

When the job is picked up by the worker and hit a retryable error, Sentry will consider the job as not retryable and send a notification while the worker will read the job class and requeue the job setting "retry" in the payload this time.

Reproduction Steps

Push a job in Redis for Sidekiq to consume through redis.lpush("queue:#{queue}", JSON.dump(msg)), do not set retry in the message payload.

Ensure the job class being processed by sidekiq has retries enabled.

Expected Behavior

Sentry should not notify if the job class consider retries

Actual Behavior

Sentry ignored the job class retry attribute and send a notification

Ruby Version

3.3.0

SDK Version

6.3.1

Integration and Its Version

No response

Sentry Config

  config.sidekiq.report_after_job_retries = true