# Troubleshooting

Most failures happen at a boundary. Start by recording the selected manager, runtime, project, plugins, and module requirements:

```sh
wago --version
wago status
wago version current
wago version which
```

## Pick the failing boundary

### [Installation and runtimes](./troubleshooting/installation-and-runtimes)
  Fix `PATH`, missing runtimes, wrong variants, and stale compiled artifacts.

### [Modules and calls](./troubleshooting/modules-and-calls)
  Diagnose validation, missing imports, exports, arguments, and feature sets.

### [Plugins and builds](./troubleshooting/plugins-and-builds)
  Separate plugin resolution, authorization, lockfile, and standalone build failures.

### [Go API and memory](./troubleshooting/go-api-and-memory)
  Fix host signatures, pointer-length checks, cancellation, and instance use.

## Report an issue

Include the exact command, complete error, OS, architecture, selected runtime, module SHA-256, and the smallest module that reproduces it. Open an issue at [github.com/wago-org/wago/issues](https://github.com/wago-org/wago/issues).