Troubleshooting

Start with lattora --version and lattora doctor. Keep the command, platform, campaign path, runner.json and console.log.

Installation and readiness

Symptom	Action
Command not found	Open a new terminal, use printed activation instructions or run `~/.local/bin/lattora`.
Unsupported platform	Use glibc Linux x86-64/ARM64 or native Apple Silicon. Check `uname -m`; avoid Rosetta.
Memory check fails	Read usable/cgroup memory in doctor. Free headroom or reduce the supported campaign/heap; minimum heap is 512 MiB.
Integrity failure	Keep diagnostics. Roll back to a healthy previous activation or restore from a trusted matching archive.
Update cannot reach GitHub	Retry the manual update when connectivity returns. The active app and offline experiments remain available.
Uninstall is locked	Exit running Lattora sessions, then retry.

Experiments and validation

Symptom	Action
Invalid properties	Use only `master.seed` and `log.level` for frozen profiles. Use explicit Stress flags for size/effort.
Smoke has no report	Expected. Run Explore for descriptive analysis.
Wrong validation directory	Select the printed campaign or exact engine run, not an arbitrary results parent.
Cancelled, timed-out or FAILED	Keep diagnostics and start a new campaign. Resume and fragment pooling are unavailable.
Research shows `NO_CLAIM`	Read the recorded reason. Degenerate SLA is a model limit; do not force a winner.

For source toolchain errors, run ./lattora.sh --check --plain. Select a full JDK 21 with both java and javac. release version 21 not supported can mean the compiler does not match the selected runtime. Installed users do not need system Java or Python. For engine bug reports, include version, OS/architecture, exact command, exit code, effective settings and relevant manifest/log excerpts. Distinguish local validation from source tests and release verification. Redact credentials or private paths before sharing. Report page errors in the docs repository.

Get started

Run experiments

Understand results

Reference

Development

Troubleshooting

Installation and readiness

Experiments and validation

​Installation and readiness

​Experiments and validation

Installation and readiness

Experiments and validation