Enum JobScheduleDispatchOutcome

Namespace

MailFathom.Application.Jobs.Scheduling

Assembly

MailFathom.Application.dll

What one pass over one schedule did about it.

public enum JobScheduleDispatchOutcome

Fields

AlreadyDispatched = 3

The occasion was already enqueued under this identity, so the job that carries it was answered with.

Two replicas reaching one occasion together is the ordinary way here, and it is the queue's own uniqueness rather than a lock that resolves it.

Dispatched = 2

The occasion was enqueued, and this pass is what wrote the job.

NotDue = 1

No occasion has passed since the one the schedule last accounted for.

PreviousRunInFlight = 4

The job the previous occasion enqueued is still pending or held, so this one stood down.

RefusedAtCapacity = 5

The queue held as much of this type as its depth allows, so the occasion was passed over.

Seeded = 0

The schedule was seen for the first time, so its occasions count from now and nothing was dispatched.

A schedule is a when rather than a debt, so the occasion that had already passed when the declaration arrived is not owed to anybody.