AdapterPoolQueueCancellationOutcome
Namespace: Meshmakers.Octo.Communication.Contracts.DataTransferObjects
What happened when a queue entry was asked to be cancelled —
DELETE {tenantId}/v1/adapterPool/{adapterPoolRtId}/queue/{executionId}.
public enum AdapterPoolQueueCancellationOutcome
Inheritance Object → ValueType → Enum → AdapterPoolQueueCancellationOutcome
Implements IComparable, ISpanFormattable, IFormattable, IConvertible
Remarks:
🔴 is a first-class outcome, not an error. The server
answers 409 Conflict for an execution that already holds a lease, because cancelling a
queued entry and interrupting a running pipeline are two different operations (concept §5,
"Cancellation"). Surfacing it as a generic failure would hide from the operator which of the
two they just failed to perform — so it travels as its own value and every surface says so.
Fields
| Name | Value | Description |
|---|---|---|
| Cancelled | 0 | The entry was waiting and is now Cancelled. It will never be leased. |
| AlreadyLeased | 1 | The execution already holds a lease (409). Nothing was cancelled. Stopping it means interrupting the running pipeline, which is the other operation. |
| NotFound | 2 | No queued execution with that id belongs to this pool (404) — it never existed here, or it already finished, failed or was cancelled. |