Enum JobEnqueueOutcome

Namespace

MailFathom.Application.Jobs

Assembly

MailFathom.Application.dll

States what enqueuing did, which is not always what it asked for.

public enum JobEnqueueOutcome

Fields

AlreadyEnqueued = 1

A job with this type and key already existed, in whatever state, and nothing was written.

Every state counts, terminal ones included: a row that succeeded is what stops the same trigger enqueuing the same work again.

Created = 0

This call created the job.

RefusedAtCapacity = 2

As many jobs of this type were already waiting as the queue accepts, so nothing was written.

This is backpressure rather than a defect: the work was neither queued nor lost, and it is the caller's to enqueue again once the queue has drained, to slow down, or to stop producing. The bound is per job type, so another type is enqueued normally while this one is full.

Remarks

Every member is an ordinary answer rather than a failure, which is why enqueuing reports a result instead of throwing. A trigger that fires twice, a synchronization retry, and a provider redelivery all reach the store with the same key, and being told the work is already queued is what they act on; a caller meeting a full queue is being told to stop producing, which is a decision it can make and an exception would only have obscured.