quartz-net

Quartz.NET 4.4.0 lets a job set context.Result to a JobRunReport (Succeeded, Failed, Cancelled or Skipped, with a summary and metrics), keeps that per job in the execution history, and adds RequireSuccessWithin health checks that degrade when a nightly job stops succeeding.

Quartz.NET 4.2.0 ships a Roslyn analyzer that rejects unparseable cron literals as QZ0001 at compile time, plus a source generator that turns [QuartzJob] and [CronTrigger] attributes into an AddDeclaredJobs() registration. Here is what it checks, what the generated code looks like, and how to opt out.

Use Quartz.NET when an LLM job must run on a real cron and never overlap itself, Hangfire when each run must survive a restart and retry on rate limits, and a plain BackgroundService only for a loose in-process loop. A decision matrix with the cron and concurrency gotchas that pick for you.