Class TriggerFiredResult
- Namespace
- Quartz.Extensibility
- Assembly
- Quartz.dll
What became of one trigger in a TriggersFired(IReadOnlyCollection<IOperableTrigger>, CancellationToken) batch.
public sealed class TriggerFiredResult
- Inheritance
-
TriggerFiredResult
- Inherited Members
Remarks
Exactly one of three things happened to each trigger the scheduler asked the store to fire, and the three factories are the only way to say so: it fired and there is a bundle to run (Fired(TriggerFiredBundle)), it turned out not to be firable after all — paused, blocked, removed, or the scheduler halted underneath it — and there is nothing to run and nothing wrong (NotFired), or firing it failed (Failed(Exception)). A result carrying both a bundle and an exception, or claiming a failure with no exception, cannot be constructed.
Properties
Exception
Why firing failed; null when it did not.
public Exception? Exception { get; }
Property Value
NotFired
The trigger did not fire, and nothing went wrong. The scheduler releases it and carries on.
public static TriggerFiredResult NotFired { get; }
Property Value
Remarks
This is the answer for a trigger that was paused, blocked by a DisallowConcurrentExecutionAttribute sibling, or removed between acquisition and firing, and for every trigger in a batch a halted scheduler never got to.
TriggerFiredBundle
What to run, when the trigger fired; null otherwise.
public TriggerFiredBundle? TriggerFiredBundle { get; }
Property Value
Methods
Failed(Exception)
Firing the trigger failed. The scheduler releases the trigger, reporting the exception.
public static TriggerFiredResult Failed(Exception exception)
Parameters
exceptionException
Returns
Fired(TriggerFiredBundle)
The trigger fired: triggerFiredBundle is what the scheduler is to run.
public static TriggerFiredResult Fired(TriggerFiredBundle triggerFiredBundle)
Parameters
triggerFiredBundleTriggerFiredBundle