SC101 means the service exited or failed to start before readiness passed.
The check did not open the workload or send SIGTERM.
| Code | SC101 FAIL |
|---|---|
| Stage | Startup and in-flight work |
| CLI exit code | 1 |
| What it means | The launched process exited, or failed to start, before the readiness route answered. |
| Messages |
|
| First thing to check | Read the captured stderr: a missing build, a bad path in command, a missing environment variable or a crash on boot. |
Where do I find the cause?
Start with Service stderr at the end of the output. Common messages include a
missing build file, an invalid environment variable, a syntax error, or an
address that is already in use.
Also check:
commandpoints to an existing executable and entry file.cwdis the directory the command expects.- The application was built before the test.
- Required environment variables are present in
env. - The process does not start in the background and let its launcher exit.
Prefer a direct command such as ["node", "dist/server.js"]. Package-manager
scripts and shell wrappers can hide the real exit or fail to forward signals.
What if the process stays alive but never becomes ready?
That is SC100. Check the configured URL, readiness path, expected status, and startup timeout.
How do I verify the fix?
Run the configured command from the configured cwd and confirm that it stays
alive. Then run shutdown-check and look for both process launched and
service ready.
If the command works in your shell but not in the test, compare environment variables and relative paths. shutdown-check does not load shell aliases or shell startup files because it launches the executable directly.