Quartz.NET 3.x

These are the documents for the 3.x line, which is maintained. Quartz.NET 4.x is the current release; the migration guide says what changed and what to do about it.

JSON Configuration

appsettings.json can configure Quartz.NET with hierarchical JSON instead of flat property keys: both scheduler properties and job/trigger definitions.

Tips

Requires Quartz 3.18 or later with the Quartz.Extensions.DependencyInjection package.

Hierarchical Properties

Instead of flat keys like "quartz.threadPool.maxConcurrency": "10", nest the JSON:

{
  "Quartz": {
    "Scheduler": {
      "InstanceName": "My Scheduler",
      "InstanceId": "AUTO"
    },
    "ThreadPool": {
      "MaxConcurrency": 10
    },
    "JobStore": {
      "Type": "Quartz.Impl.AdoJobStore.JobStoreTX, Quartz",
      "DataSource": "default",
      "TablePrefix": "QRTZ_"
    },
    "DataSource": {
      "default": {
        "Provider": "SqlServer",
        "ConnectionString": "Server=localhost;Database=quartznet"
      }
    },
    "Plugin": {
      "jobHistory": {
        "Type": "Quartz.Plugin.History.LoggingJobHistoryPlugin, Quartz.Plugins"
      }
    },
    "Serializer": {
      "Type": "stj"
    }
  }
}

Each JSON path segment becomes a dot-separated segment of the flat key, with PascalCase converted to camelCase. From 3.22.7 a name you choose keeps its case: an execution-limit group, a Context:Key key, and a data source, job listener or trigger listener name. An execution-limit key keeps its :. A plugin's name is still camel-cased, because the XML plugin names its stored jobs after it.

JSON Path	Flat Property Key
`Scheduler:InstanceName`	`quartz.scheduler.instanceName`
`ThreadPool:MaxConcurrency`	`quartz.threadPool.maxConcurrency`
`DataSource:default:Provider`	`quartz.dataSource.default.provider`
`ExecutionLimit:Reports`	`quartz.executionLimit.Reports` (3.22.7; `reports` before)
`Plugin:JobHistory:Type`	`quartz.plugin.jobHistory.type`

Usage with DI

services.AddQuartz(Configuration.GetSection("Quartz"), q =>
{
    // Additional code-based configuration still works alongside JSON
    q.AddJob<MyJob>(j => j.WithIdentity("codeJob").StoreDurably());
});

Usage without DI

var properties = QuartzConfigurationHelper.ToNameValueCollection(
    Configuration.GetSection("Quartz"));
var factory = new StdSchedulerFactory();
factory.Initialize(properties);

Backward Compatibility

Flat keys still work, and both styles can be mixed in one section:

{
  "Quartz": {
    "quartz.scheduler.instanceId": "AUTO",
    "ThreadPool": {
      "MaxConcurrency": 10
    }
  }
}

JSON Scheduling Data

Define jobs and triggers in appsettings.json under a Schedule sub-section:

{
  "Quartz": {
    "Scheduler": {
      "InstanceName": "My Scheduler"
    },
    "Schedule": {
      "Jobs": [
        {
          "Name": "sampleJob",
          "Group": "sampleGroup",
          "JobType": "MyApp.Jobs.SampleJob, MyApp",
          "Description": "A sample job",
          "Durable": true,
          "Recover": false,
          "JobDataMap": {
            "connectionString": "Server=localhost",
            "retryCount": "3"
          }
        }
      ],
      "Triggers": [
        {
          "Name": "cronTrigger",
          "JobName": "sampleJob",
          "JobGroup": "sampleGroup",
          "Description": "Fires every 10 seconds",
          "Cron": {
            "Expression": "0/10 * * * * ?",
            "TimeZone": "UTC"
          }
        }
      ]
    }
  }
}

Trigger Types

Each trigger has exactly one schedule object; which one is present sets the trigger type.

Simple Trigger

{
  "Name": "simpleTrigger",
  "JobName": "myJob",
  "Simple": {
    "RepeatCount": -1,
    "Interval": "00:00:10",
    "MisfireInstruction": "SmartPolicy"
  }
}

RepeatCount: Number of times to repeat. Use -1 for indefinite, 0 for fire once.
Interval: TimeSpan string (e.g., "00:00:10" for 10 seconds, "01:00:00" for 1 hour).

Cron Trigger

{
  "Name": "cronTrigger",
  "JobName": "myJob",
  "Cron": {
    "Expression": "0/30 * * * * ?",
    "TimeZone": "America/New_York",
    "MisfireInstruction": "DoNothing"
  }
}

Calendar Interval Trigger

{
  "Name": "calendarTrigger",
  "JobName": "myJob",
  "CalendarInterval": {
    "RepeatInterval": 1,
    "RepeatIntervalUnit": "Day",
    "MisfireInstruction": "SmartPolicy"
  }
}

RepeatIntervalUnit values: Second, Minute, Hour, Day, Week, Month, Year.

Daily Time Interval Trigger

{
  "Name": "businessHoursTrigger",
  "JobName": "myJob",
  "DailyTimeInterval": {
    "RepeatInterval": 15,
    "RepeatIntervalUnit": "Minute",
    "RepeatCount": -1,
    "StartTimeOfDay": "08:00:00",
    "EndTimeOfDay": "17:00:00",
    "DaysOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
    "TimeZone": "America/Chicago"
  }
}

Common Trigger Fields

All trigger types support these fields:

Field	Description
`Name`	Trigger name (required)
`Group`	Trigger group (defaults to DEFAULT)
`JobName`	Associated job name (required)
`JobGroup`	Associated job group (defaults to DEFAULT)
`Description`	Trigger description
`Priority`	Trigger priority (integer)
`CalendarName`	Calendar to apply
`StartTime`	ISO 8601 start time (e.g., `"2024-01-01T00:00:00Z"`)
`StartTimeSecondsInFuture`	Start time as seconds from now (mutually exclusive with StartTime)
`EndTime`	ISO 8601 end time
`JobDataMap`	Key-value pairs for the trigger's data map

Multiple Named Schedulers

Each child of a Schedulers sub-section is registered as a named scheduler:

{
  "Quartz": {
    "Schedulers": {
      "Primary": {
        "Scheduler": {
          "InstanceId": "AUTO"
        },
        "ThreadPool": {
          "MaxConcurrency": 10
        },
        "Schedule": {
          "Jobs": [
            {
              "Name": "primaryJob",
              "JobType": "MyApp.Jobs.PrimaryJob, MyApp",
              "Durable": true
            }
          ],
          "Triggers": [
            {
              "Name": "primaryTrigger",
              "JobName": "primaryJob",
              "Cron": { "Expression": "0/10 * * * * ?" }
            }
          ]
        }
      },
      "Secondary": {
        "ThreadPool": {
          "MaxConcurrency": 5
        }
      }
    }
  }
}

// Registers "Primary" and "Secondary" named schedulers automatically
services.AddQuartz(Configuration.GetSection("Quartz"));
services.AddQuartzHostedService();

Each named scheduler section supports the same hierarchical properties, a Schedule sub-section with Jobs/Triggers, and code-based overrides.

To register one named scheduler explicitly, pass the named overload either the scheduler's own section or the root Quartz section; from the root it finds the matching Schedulers:{name} sub-section:

// Both lines are equivalent
services.AddQuartz("Primary", Configuration.GetSection("Quartz"));
services.AddQuartz("Primary", Configuration.GetSection("Quartz:Schedulers:Primary"));

Warning

A Schedulers sub-section together with top-level scheduler configuration (e.g., Scheduler, ThreadPool) is an error; use one or the other. A top-level Schedule/Scheduling section cannot be combined with Schedulers either: move it under the right Schedulers:{name} entry.

Standalone JSON Files (quartz_jobs.json)

For file-based scheduling with hot reload, use JsonSchedulingDataProcessorPlugin from the Quartz.Plugins package; see Quartz Plugins.

The file uses the same Jobs and Triggers format as the Schedule section, in an envelope with optional PreProcessingCommands and ProcessingDirectives:

{
  "PreProcessingCommands": {
    "DeleteJobsInGroup": ["obsoleteGroup"],
    "DeleteTriggersInGroup": ["oldTriggerGroup"],
    "DeleteJobs": [
      { "Name": "oldJob", "Group": "DEFAULT" }
    ],
    "DeleteTriggers": [
      { "Name": "oldTrigger" }
    ]
  },
  "ProcessingDirectives": {
    "OverWriteExistingData": true,
    "IgnoreDuplicates": false,
    "ScheduleTriggerRelativeToReplacedTrigger": false
  },
  "Schedule": {
    "Jobs": [
      {
        "Name": "myJob",
        "JobType": "MyApp.Jobs.MyJob, MyApp",
        "Durable": true
      }
    ],
    "Triggers": [
      {
        "Name": "myTrigger",
        "JobName": "myJob",
        "Cron": {
          "Expression": "0/30 * * * * ?"
        }
      }
    ]
  }
}

PreProcessingCommands

Run before scheduling. All fields are optional:

Field	Description
`DeleteJobsInGroup`	Array of group names. Use `"*"` to delete jobs in all groups.
`DeleteTriggersInGroup`	Array of group names. Use `"*"` to delete triggers in all groups.
`DeleteJobs`	Array of `{ "Name": "...", "Group": "..." }` objects. Group is optional.
`DeleteTriggers`	Array of `{ "Name": "...", "Group": "..." }` objects. Group is optional.

ProcessingDirectives

Field	Default	Description
`OverWriteExistingData`	`true`	Replace existing jobs/triggers with the same identity.
`IgnoreDuplicates`	`false`	When `OverWriteExistingData` is `false`, silently skip duplicates instead of erroring.
`ScheduleTriggerRelativeToReplacedTrigger`	`false`	Adjust new trigger timing based on old trigger's last fire time.