Micro states
While a scenario runs, each micro shows its state. These are the possible ones:
| State | Meaning |
|---|---|
| Stopped | Stopped: it hasn’t been started or has already stopped. |
| Installing | Running its pre-steps (install dependencies, build…) before starting. |
| Starting | Starting: the process is running but its health doesn’t respond healthy yet. |
| Healthy | Healthy: its health probe responds correctly. Ready to receive calls. |
| Unhealthy | Running, but its health doesn’t respond healthy. |
| Crashed | The process ended unexpectedly. Look at its logs and the diagnosis. |
The normal path is Stopped → Starting → Healthy. If a micro doesn’t manage to start
(wrong command, missing repo, occupied port), the reason is usually in the engine
logs, not the micro’s: see Debug a micro that won’t
start.
Infrastructure
Section titled “Infrastructure”The infrastructure has its own states: Stopped, Starting, Healthy and Unhealthy.