Anomaly

​

Inputs

• Data in — value to pass through. Optionally captured into the anomaly’s params under Param key so consumers can report it back.
• Entity ID — optional Twine-internal UUID of the entity the anomaly is about. Populates the row’s entity_id column for the auto-resolve sweep and rich entity rendering in the UI.
• External ID — optional source-system identifier for the entity. Always populate this in convert_from_system flows: at that pipeline stage, the only id available is the remote one.

​

Outputs

• Result — the input value, unchanged.

​

Schema

• Code — short stable identifier (e.g. missing_phone).
• Severity — info / warning / critical. Influences how consumers triage and surface the anomaly.
• Message — human-readable description shown to the customer.
• Param key — optional. When set, the inbound value is attached to the anomaly under this key, so the message template can reference it.

​

Ports