PipelineExecutionFailureKind
Namespace: Meshmakers.Octo.Communication.Contracts.DataTransferObjects
What a failed pipeline execution says about its writes (rule R3 of the method consistency model).
Values must match the CK model enum System.Communication/PipelineExecutionFailureKind.
public enum PipelineExecutionFailureKind
Inheritance Object → ValueType → Enum → PipelineExecutionFailureKind
Implements IComparable, ISpanFormattable, IFormattable, IConvertible
Remarks:
The adapter classifies the exception that ended the execution with
Meshmakers.Octo.Runtime.Contracts.UnacknowledgedWriteClassifier and reports the result next to
PipelineExecutionStatus.Failed. The communication controller stores it on the execution and a
pipeline method handler answers METHOD_OUTCOME_UNKNOWN (with a correlation id) on
PipelineExecutionFailureKind.OutcomeUnknown instead of METHOD_HANDLER_FAILED.
A structured field, never a marker in the error message: the error message is free text for people and is never parsed.
Fields
| Name | Value | Description |
|---|---|---|
| Failed | 0 | An ordinary failure: the database refused the write, or the pipeline failed for another reason. The caller of a pipeline method gets METHOD_HANDLER_FAILED. |
| OutcomeUnknown | 1 | A write was neither acknowledged nor refused (MongoDB write-concern error, UnknownTransactionCommitResult): it may have taken effect. The caller of a pipeline method gets METHOD_OUTCOME_UNKNOWN. |