Debug Guide

Use this guide to trace bugs, performance issues, or flow errors during development or production.

---

Log Output

• All backend logs are printed to the terminal.

• Use LOG_LEVEL=debug in .env to increase verbosity.

• Each node execution prints input/output for visibility.

---

Inspect Flow Executions

• Click on a node in the UI after running a flow to inspect:

  • Node input

  • Output

  • Error (if any)

This allows step-by-step inspection without leaving the browser.

---

Testing API Calls

• Use tools like curl, Postman, or Insomnia to test flow endpoints.

• All flows expose a public API route (if enabled).

• Always include input JSON in the body.

---

Database Issues

• For SQLite: ensure the file path is writable and persistent.

• For Postgres: verify credentials and port binding.

• Look for connection errors in startup logs.

---

Hot Reloading

During development:

• Most changes in the backend auto-reload with nodemon (if configured).

• Frontend hot-reloads via Vite/Next.js dev server.

If changes don’t reflect:

• Clear .next or dist folder

• Restart npm run dev