Skip to main content
While you work, Leapter keeps checking your whole project for problems: a value of the wrong type, a call to a Blueprint that doesn’t exist, or a private Blueprint that nothing calls. Everything it finds is listed in the Findings panel, so you can fix problems before you test or release.

Open the Findings panel

Click the Findings tab in the right sidebar of the Blueprint Editor. When the project has errors, the tab shows a red badge with their number. The panel groups the findings by Blueprint, and within a Blueprint by the rule that found them. The header counts the errors and the warnings of the whole project. Each finding has one of two levels: When the project is clean, the panel reads No findings across this project.

An example

In the Quick Affordability Check, the step Start with the requested instalment starts the total with the requested instalment, an amount. Suppose it assigns a text instead: totalMonthlyPayments = "none". Leapter reports a warning right away, without a run:
The editor with the section Add Up Monthly Payments of the Quick Affordability Check. The step Start with the requested instalment reads totalMonthlyPayments = “none” and carries a warning badge with the number 1. The Findings panel on the right counts 1 warning and lists it under Quick Affordability Check, rule Value does not match the declared type, with the message 'totalMonthlyPayments' is number, but this value is text.

A text assigned to a number shows up as a warning in Findings and as a badge on the step.

The panel lists the warning under the Blueprint (Quick Affordability Check) and the rule that found it (Value does not match the declared type), with the message ‘totalMonthlyPayments’ is number, but this value is text. The step carries a badge with the number of its findings.

Work through a finding

For each finding you can:
  • Go to this finding: jump to the node or definition it is about. The node also carries a badge in the diagram, so you can spot problems while you read the logic.
  • Fix with AI: hand the finding to the Lab Agent. The agent proposes a fix, and you review it like any other agent change before it is applied.
Leapter re-checks the project after every change. To run a full check yourself, click Re-check the whole project.
Findings don’t stop you from editing or testing, so you can work through them in the order that suits you. Resolve them before you release a version to production.

What to do next

  • Test your Blueprint: run the logic with your own values once the findings are resolved
  • Test Suites: keep the fixed behavior covered by tests
  • Lab Agent: ask the agent to review the whole project with /review