SC112 means the process or workload ended after the start barrier passed but
before shutdown-check sent SIGTERM. The gap is short, so the test workload is
usually only barely long enough.
| Code | SC112 FAIL |
|---|---|
| Stage | Startup and in-flight work |
| CLI exit code | 1 |
| What it means | The service or a workload request finished in the moment before the signal was sent. |
| Message |
|
| First thing to check | Make the test workload slower than the time it takes to start it, so it is still running when SIGTERM arrives. |
How do I fix it?
Make the workload clearly longer than the time needed to confirm its start and send the signal. A controlled delay of one or two seconds is usually enough.
Also check that:
- the service is not designed to exit after one request;
- the probe does not report active work too late;
- a timer or background task is not stopping the process;
- the test route behaves consistently on a busy CI runner.
Do not solve this by increasing shutdown.deadlineMs; that timer starts after
the signal and does not affect this gap.
How do I verify the fix?
The corrected timeline shows signal sent immediately after
work confirmed active, with no process-exit or request-finished event between
them. Run it several times on the slowest CI environment to make sure the
timing margin is reliable.
If the service itself exits in this gap, inspect application logs for a timer, one-shot mode, or unhandled error rather than extending the workload.