ETyped Error Handling in Service Pipelines
Consumes the typed error side output of Input, Process or Sink.
When to use
Use Error to model recovery, logging or dead-letter handling as a normal branch.
Behavior
- The parent operator owns the error relationship.
- The error branch can continue through ordinary operators.
General properties
Identity, ownership and operator-specific mode.
typeTransformationTypeOperator kind. It controls available properties, valid sources and generated interfaces.
RequiredAllowed:Input, SubStream, Map, Filter, Join, MultiJoin, Process, FlatMap, FlatMapIterable, KeyBy, Merge, Split, Case, Sink, CycleLink, Error, Delay, WhennamestringHuman-readable stream name shown in the designer and used to derive default generated symbols.
RequiredserviceServiceService that owns the stream. Connected streams must belong to the same service.
RequiredConnections properties
Upstream graph references accepted by this operator.
sourceStreamSingle upstream stream. The designer only offers structurally and type-compatible candidates.
RequiredData Types properties
Message contracts visible at this node.
valueTypeTypeOutput or response message contract. The exact meaning is operator-specific.
RequiredDefault:UnknownTypeExecution properties
Pipeline placement and runtime policy.
pipelinestringNamed business-flow grouping inside the owning service; retained in generated configuration and runtime grouping metadata. It does not create connections.
Position properties
Designer-only canvas coordinates.
xPosnumberHorizontal designer coordinate. It has no runtime effect; missing positions can be supplied by layout.
yPosnumberVertical designer coordinate. It has no runtime effect; missing positions can be supplied by layout.
Configuration example
type: Error
source: saveOrder
valueType: error