Local runtime troubleshooting
Experimental
The local build and runtime are experimental. The tsm runtime commands, their behaviour and configuration may still change.
Start with tsm --workspace demo runtime status; add --json for full details.
| Problem | Check with | What to do |
|---|---|---|
Phase NOT_CREATED | runtime plan PROFILE | Finish the profile and prerequisites, then runtime up PROFILE |
Phase STOPPED | runtime status | Start it with runtime up; there is no automatic fallback to a remote environment |
Phase WAITING_EXTERNAL | runtime ide COMPONENT --json | Start that component in the IDE |
RUNNING, but a row is unhealthy | runtime logs COMPONENT --tail 100 | Inspect that component; the phase alone does not mean ready |
| Profile changed while running | runtime status --json | runtime down, then runtime up with the new profile; data is kept |
| Missing seed or checksum | runtime plan full | Get the verified seed from your delivery owner; never invent a checksum |
Unknown backend/defaults keys | Runtime profiles | Convert the old profile file to the service catalog format |
When reporting a problem, attach the human runtime status output and the relevant logs. Review raw Docker
metadata and generated argfiles before sharing; they may contain deployment-specific secrets.