Best practice to handle phantom jobs in production

[aimanalrafi]

We're seeing recurring Unable to find corresponding Quartz trigger for job ... warnings in production after removing a @Scheduled method. It appears Quartz retains "phantom jobs" in its DB even though the corresponding scheduled method no longer exists in code.

Is this expected behavior in production environments? Shouldn't Quartz automatically clean these up, or at least provide a safer migration path? The closest thing I found to this is this

What’s the recommended approach in production avoiding or automatically handling orphaned job entries when scheduled methods are refactored or deleted?