The Broken Health Check

Instances that can still serve user traffic are removed during deploy whenever an optional analytics dependency is unavailable.

Initial failing signalLiveness health fails when optional analytics is downExpected behavior: 200 ok while process is alive · actual behavior: 503 analytics unavailable

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Compare the health endpoints when the optional dependency is available and unavailable.
Trace which signals the deployment platform uses to keep an instance alive.
Separate the endpoint responsibilities without hiding real process failures.

Focus Mode

Start

src/health.js

Likely area

src/health.js

Challenge Coach

Hints reveal broad direction first, then narrow toward the suspect path without showing hidden tests or exact solution code.

TopicDeployment

DifficultyEasy

Est. time16 min

Workspacepreparing

Explorer

Loading files

Evidence Map

Failing signal loaded from challenge API
Workspace files loaded from workspace API
Results rendered only after API run/submit

Autosaved

workspace

Outputread-onlyready$ prepare workspace

Preparing workspace