Breakpoint

Marks a debug pause point for an eligible replay-enabled execution.

When to use

Use it while investigating the order or timing of control paths in a supported debug run.

Example

Place a Breakpoint before Order to inspect the recorded values immediately before submission.

Try it here

Explore Breakpoint

Marks a debug pause point for an eligible replay-enabled execution.

Exercise steps

1. Edit the breakpoint label and inspect its Next outcome.
2. Follow the connected activation; stopping on a breakpoint belongs to debug replay.

Start lesson

Inspect before an action

Place Breakpoint on the control path before Order and give it a label such as Before submission. In a supported recorded debug or replay workflow, inspect the values present at that point, then compare them with the subsequent Order outcome. Its Next branch keeps the graph's intended path visible. A Breakpoint on the canvas does not by itself pause a live browser or exchange order, and it is not a guarantee that every Backtest profile offers interactive stepping. Check the available debug controls for the selected run.

Common problems

It affects debug behavior only when the run records the required data. It does not pause normal editing or make replay available.

Next steps

Review the generated Parameters, Outcomes, and Data Ports on this page, then open the related guides for the complete workflow.