Expand description
What a flow run did — the trace (doc 48 “Traces: what the flow did,
visible everywhere”). The engine appends one TraceStep per node it
executes and ends with a FlowOutcome. The daemon maps this to call
events (a flow timeline in Call details) and to the push uploader that
syncs it to the platform; the editor later overlays step counts on the
flow diagram.
Serializable and self-contained (references node ids and small enums, no daemon types) so it travels unchanged from the engine core to events, storage, and the wire. This is an output format, not the document shape — so it is hand-written here, not generated from the schema.
Structs§
- Trace
- The full record of one run of a flow against one caller.
- Trace
Step - One executed node and what happened there.
Enums§
- Flow
Outcome - How a run ended — the call disposition (“Answered by your receptionist”, “Left a message”, …) and the debugging outcome for abnormal ends.
- Step
Detail - The per-node outcome. Tagged so it serializes to a self-describing object the renderer can switch on.