In a draft test run, set a breakpoint to pause before a step and inspect the run’s data, mock an API call’s response, supply a reviewer’s answer or skip a wait, or reuse a step’s output from an earlier run to reproduce a hard case without calling the real system; published runs execute every step for real. In production, open a run to its steps, calls, errors and final data, with the logs grouped by step and linked to the canvas, then use the metrics and logs across runs to tell one bad run from a dependency failing everywhere.
- Breakpoints and mocks
- Pause a test run and inspect it, or substitute a response
- Retry from the failure
- A new run that resumes where the failed one stopped
- Run logs
- Grouped by step and linked to the canvas
- Across every run
- Metrics, alerts and export to OpenTelemetry