Class SchedulingOptions

Namespace

Quartz

Assembly

Quartz.dll

What happens to a job or a trigger that is declared up front and whose key the scheduler already knows.

public sealed class SchedulingOptions

Inheritance

object

SchedulingOptions

Inherited Members

object.Equals(object)

object.Equals(object, object)

object.GetHashCode()

object.GetType()

object.ReferenceEquals(object, object)

object.ToString()

Remarks

This is Scheduling, and it governs every declared job and trigger, however it was declared: AddJob and AddTrigger inside AddQuartz(…), the Quartz:Scheduling configuration section, and a scheduling file read by the XML or JSON plugin. It says nothing about IScheduler's own members, which take their own AddJobOptions and ScheduleJobOptions.

Properties

IgnoreDuplicates

Whether a declared job or trigger whose key is already stored is passed over rather than reported.

public bool IgnoreDuplicates { get; set; }

Property Value

bool

Remarks

Only consulted when OverwriteExistingData is off, since replacing is already an answer to a duplicate key — and setting this one is enough to turn it off, since its default is not a statement. Setting both explicitly is refused at startup rather than resolved silently in favour of replacing, which is the opposite of what asking for this one means.

See Also

OverwriteExistingData

OverwriteExistingData

Whether a declared job or trigger replaces one already stored under the same key.

public bool OverwriteExistingData { get; set; }

Property Value

bool

Remarks

On by default. Turning it off makes a duplicate key an error, unless IgnoreDuplicates says to pass over it instead.

The default is a default rather than a statement: setting IgnoreDuplicates and leaving this one alone turns it off, because "pass over what is already there" and "replace what is already there" cannot both be meant and only one of them was asked for. Setting both explicitly is still refused at startup.

See Also

IgnoreDuplicates

ScheduleTriggerRelativeToReplacedTrigger

Whether a replaced trigger hands its firing history to the trigger replacing it.

public bool ScheduleTriggerRelativeToReplacedTrigger { get; set; }

Property Value

bool

Remarks

Only consulted when OverwriteExistingData is on, since nothing is replaced otherwise. The new trigger adopts the old one's last fire time, and computes its next fire time from there rather than from its own start time — so restarting an application does not re-fire a schedule that has already run.