Documentation
¶
Overview ¶
Example 15: step breakpoints — stop a DAG line at a specific step, inspect intermediate state, then continue.
A breakpoint is declared on a step with BreakBefore(labels...) (the step stays pending, never dispatched) or BreakAfter(labels...) (the step runs and its result is persisted, but its direct dependents are held). Breakpoints are inactive by default: the same DAG submitted without WithActiveBreakpoints runs straight through. Only the lines that hit an armed breakpoint stop — independent parallel branches keep running.
ResumeBreakpoint is debugger "continue": it releases whatever is currently stopped on a label, and the label stays armed for later steps (including dynamically added ones). All breakpoint state lives in NATS KV, so blocked DAGs survive restarts and can be resumed from any process — or from the CLI:
ebctl dag bp ls <dag-id> ebctl dag bp resume <dag-id> <label>
Source Files