Shutdown Check

Search documentation

Find a page or section

SC999: Unexpected error

shutdown-checkv1.0.1View as Markdown

SC999 (unexpected error) means shutdown-check itself hit an error it did not plan for. Read the message, check the config, or report it with the timeline.

SC999 means shutdown-check caught an error that does not belong to a normal failure stage. The message comes from the original error, so it is the best place to start.

CodeSC999 FAIL
StageUnexpected errors
CLI exit code1
What it meansThe check itself hit an error it did not expect, such as an unsafe request path or an operating-system failure.
Message
    First thing to checkRead the message in the result; if it points at shutdown-check rather than your service, open an issue with the timeline.

    What should I do first?

    1. Read the full message and the last timeline event.
    2. If you call runCheck() directly, validate the object with parseConfig().
    3. Try the same config through checkShutdown() or the CLI.
    4. Confirm the environment is supported and has enough system resources.

    A hand-built CheckConfig can bypass normal validation and cause errors such as an unsafe request path. The higher-level APIs catch those values before the run begins.

    When should I report a bug?

    Report the problem when a valid config repeatedly returns SC999. Include the package version, operating system, Node.js version, config with secrets removed, result message, timeline, and a small reproduction if possible.

    How do I rule out a config problem?

    Run the same input through parseConfig() or use the CLI. If validation rejects it, fix that error first. If validation passes and SC999 repeats, keep the original message unchanged for the issue report.

    Never include credentials, private URLs, tokens, or customer data in the reproduction.