[10.x] Remember the job on the exception

[timacdonald]

When these exceptions are triggered they pass through the applications handlers reporting piping.

It is be common for a certain type of job to be okay to timeout and be treated "special", e.g., log it but not to a 3rd party error monitoring.

Currently the only way to do this is to check the error message, .e.g.,

if (
    $e instanceof MaxAttemptsExceededException &&
    str_starts_with($e->getMessage(), MySpecialJob::class.' ')
) {
    //
}

While not the end of the world, it feels a flaky and yuck. This exposes the job on the exception.

if (
    $e instanceof MaxAttemptsExceededException &&
    $e->job->getResolvedJob() instanceof MySpecialJob
) {
    //
}

[driesvints]

@timacdonald looks good. What are your thoughts on the job having a large payload and thus filling up logs when being reported?

[timacdonald]

@driesvints my understanding is that custom properties on exceptions are ignored when reporting or logging.

I've never seen attaching a property to an exception class cause any issues.

See also: #47223 (comment)

[driesvints]

@timacdonald yup, you're totally right! 👍