Enum DataflowError 

#[non_exhaustive]
pub enum DataflowError {
    Validation(String),
    FunctionExecution {
        context: String,
        source: Option<Box<DataflowError>>,
    },
    Workflow(String),
    Task(String),
    FunctionNotFound(String),
    Deserialization(String),
    Io(String),
    LogicEvaluation(String),
    Http {
        status: u16,
        message: String,
    },
    Timeout(String),
    Unknown(String),
    Service {
        kind: String,
        message: String,
        detail: Option<String>,
        retryable: bool,
    },
}

Main error type for the dataflow engine

#[non_exhaustive]: a downstream match needs a wildcard arm. Adding it here makes every future variant additive rather than a breaking change, which matters because this enum is the crate’s error channel and will keep growing.

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

Validation(String)

Validation errors occurring during rule evaluation

FunctionExecution

Errors during function execution

Fields

context: String

source: Option<Box<DataflowError>>

Workflow(String)

Workflow-related errors

Task(String)

Task-related errors

FunctionNotFound(String)

Function not found errors

Deserialization(String)

JSON serialization/deserialization errors

Io(String)

I/O errors (file reading, etc.)

LogicEvaluation(String)

JSONLogic/DataLogic evaluation errors

Http

HTTP request errors

Fields

status: u16

message: String

Timeout(String)

Timeout errors

Unknown(String)

Any other errors

Service

A failure the service layer classifies itself.

The engine never interprets kind: it carries it to ErrorInfo::code and otherwise treats this exactly like any other error — continue_on_error, the audit-trail entry and the Result::Err short-circuit are unchanged. No built-in returns this variant.

Display renders message alone, so to_string() is always safe to hand to an untrusted caller. detail is reachable only through Debug, DataflowError::detail and ErrorInfo::detail.

Build it with DataflowError::service.

Fields

kind: String

Stable, service-owned classification, e.g. "circuit_open".

message: String

Caller-safe text.

detail: Option<String>

Operator-only text: logged and kept on the trace, not intended for an untrusted caller.

retryable: bool

Retryability, declared by the service rather than inferred from the variant.

Implementations

impl DataflowError

pub fn function_execution<S: Into<String>>( context: S, source: Option<DataflowError>, ) -> Self

Creates a new function execution error with context

pub fn http<S: Into<String>>(status: u16, message: S) -> Self

Creates a new HTTP error

pub fn from_io(err: Error) -> Self

Convert from std::io::Error

pub fn from_serde(err: Error) -> Self

Convert from serde_json::Error

pub fn retryable(&self) -> bool

Determines if this error is retryable (worth retrying)

Retryable errors are typically transient infrastructure failures that might succeed on retry. Non-retryable errors are typically data validation, logic, or configuration errors that will consistently fail on retry.

pub fn kind(&self) -> Option<&str>

The service-owned classification, or None for every engine-owned variant.

This is the whole point of DataflowError::Service: a handler can classify its own failures with a stable code the engine never interprets.

pub fn detail(&self) -> Option<&str>

Operator-only detail, if this is a DataflowError::Service carrying one.

Never included in Display, so to_string() stays safe to hand to an untrusted caller. Reachable through Debug, this method, and ErrorInfo::detail.

pub fn service( kind: impl Into<String>, message: impl Into<String>, ) -> ServiceErrorBuilder

Start building a service-classified error.

kind is the stable code the service will switch on; message is the caller-safe text. Defaults: no detail, retryable: false.

use dataflow_rs::DataflowError;

let e = DataflowError::service("circuit_open", "upstream unavailable")
    .detail("connector 'billing' breaker open")
    .retryable(true)
    .build();

assert_eq!(e.kind(), Some("circuit_open"));
assert_eq!(e.detail(), Some("connector 'billing' breaker open"));
assert!(e.retryable());
// Display carries only the caller-safe text.
assert_eq!(e.to_string(), "upstream unavailable");

Trait Implementations

impl Clone for DataflowError

fn clone(&self) -> DataflowError

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for DataflowError

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for DataflowError

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Display for DataflowError

fn fmt(&self, __formatter: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Error for DataflowError

fn source(&self) -> Option<&(dyn Error + 'static)>

Returns the lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0:

use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0:

replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type-based access to context intended for error reports.

impl Serialize for DataflowError

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.