Table of Contents

Enum ExecutionOutcome

Namespace
Quartz
Assembly
Quartz.dll

How one firing of a trigger ended.

public enum ExecutionOutcome

Fields

Cancelled = 2

The job was interrupted: the firing's cancellation token was signalled and the job stopped rather than finished. Matches OnCancellation.

Failed = 1

The job ran and threw. Matches OnFailure.

Reported for every failed run, the ones the trigger answers with a retry included: the job did run and it did throw. What tells the two apart is Instruction — RetryTrigger when the occurrence has an attempt left.

NotExecuted = 4

The occurrence did not happen at all — the job could not be instantiated, a listener abandoned it before execution, or the scheduler could not dispatch it. Matches no ContinuationCondition: nothing happened, so nothing is settled and a continuation waiting on this trigger keeps waiting.

Succeeded = 0

The job ran and returned. Matches OnSuccess.

Vetoed = 3

A trigger listener vetoed the firing, so the job never ran. Matches OnVeto.

Remarks

The run shell classifies every firing it completes, and hands the answer to the job store on Outcome. What the store does with it is release or discard the continuations waiting on that trigger.

It says what the firing did, and nothing about what the schedule makes of it. A job that ran and threw is Failed whether or not its RetryPolicy then asked for another attempt — that request is RetryTrigger, on Instruction, and it is what tells a store the occurrence is not finished. Settling continuations is skipped on that instruction rather than on the outcome, so a store reading the outcome alone never mistakes an attempt for a verdict.

See Also