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. Each finding is either an error — something that keeps the logic from working as written — or a warning — something that works but is probably not what you intended. When the project is clean, the panel reads No findings across this project.

​
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