How To's
Short, task-shaped recipes. Each page answers one question; the Tutorial is the place to start if you are new to Quartz.NET.
- One-Off Job — fire a job once, now or at a given time
- Rescheduling Jobs — change a live schedule, retry a firing, recover a failed trigger
- Retrying Failed Jobs — give a trigger a retry policy, and what it does and does not do
- Multiple Triggers — drive one job from several triggers, and give each its own data
- Job Template — the recommended skeleton for a job class
- Running Quartz under Aspire — telemetry, health and the database, wired to an AppHost
- Quartz.NET with Wolverine — cron-publishing into a message bus, cancelling by correlation, and sharing the outbox's transaction
- Embedding Quartz in a Library — for a package that has to fit into an application it does not own
- Running under an External Leader Election — one instance, started and stopped by somebody else's election
- Publishing Trimmed and Native AOT — what each package claims, what still warns, and what to do about it
Extending Quartz — start with the index, then the four seams the Quartz.Impl.AdoJobStore types exist for:
- Extending Quartz — what is open, what is closed and why, and how to ask for a seam
- A Job Store of Your Own — keeping scheduling data somewhere new, or decorating a store
- A Driver Delegate for a New Database — supporting a database Quartz does not ship a dialect for
- Persisting a Custom Trigger Type — storing a trigger family of your own without a blob
- A Lock Handler of Your Own — replacing the
QRTZ_LOCKSrow with something else
Reference material that these recipes lean on:
- Cron Expression Reference — the cron field and special-character syntax
- Configuration Reference — every option, typed and legacy
