Execution history

Every run is recorded locally — browse past runs, open their full detail, and compare then with now.

Bandura records every flow run in a local history — nothing is sent anywhere. It answers the two questions that come up constantly: did this pass yesterday? and what exactly did it return last time?

Browsing runs

Open the bottom panel (⌘J) and pick the History tab. Each row is one run: status (passed/failed), flow name, when it ran, and how long it took.

Run detail

Click a row to open the full record of that run — per-node outcomes, error messages, and the result snapshot as it was at the time. This makes regressions concrete: open the last green run, open the red one, and diff by eye what the API returned differently.

The Result tab at the top of the flow editor always shows the latest run’s summary for the open flow; History is where the older ones live.

Clearing history

Need a clean slate? Clear history at the top of the History tab deletes every recorded run. It asks for confirmation first, and it can’t be undone — but it only touches your local run log, never your flows or any other data.

Where it’s stored

History is a local database inside your Bandura profile on this machine. It isn’t part of the workspace, so it’s never committed to Git and doesn’t travel with the repo — your test files stay clean, your run log stays yours.