Enum StoredTriggerState

Namespace

Quartz.Extensibility

Assembly

Quartz.dll

The state a job store keeps a trigger in.

public enum StoredTriggerState

Fields

Acquired = 1

A scheduler instance has reserved the trigger and intends to fire it.

Blocked = 4

Held back because its job disallows concurrent execution and is already running.

Complete = 3

The trigger has no further fire times and is awaiting removal.

Deleted = 8

The trigger does not exist. A sentinel a read reports rather than a value a store writes.

Error = 5

The trigger could not be fired — typically its job type would not load — and will not be retried until it is reset.

Executing = 2

The trigger is firing. The ADO.NET store writes this to FIRED_TRIGGERS rather than to TRIGGERS, where it only turns up through migrated or hand-repaired data.

Paused = 6

Paused, either individually or as part of its group.

PausedBlocked = 7

Paused while also blocked, so that resuming returns it to Blocked rather than to Waiting.

Waiting = 0

Schedulable: the trigger is waiting for its next fire time to arrive. The default, and the state a stored value this version does not recognise is treated as.

Remarks

This is storage's own vocabulary, not the one callers see: TriggerState is what a scheduler reports, and one is derived from the other (plus whether an execution is in flight) by Resolve(StoredTriggerState, bool) rather than mapped one to one. Every job store — the in-memory one, the ADO.NET one and a custom IJobStore alike — keeps its triggers in this vocabulary and resolves through the same precedence, so two stores cannot report different states for the same situation.

The ADO.NET job store persists these as the same strings the TRIGGER_STATE and STATE columns have always held — Quartz.Impl.AdoJobStore.StoredTriggerStates is the only place the two representations meet, and the strings themselves stay on AdoConstants, which is that store's schema contract.