A container's `HEALTHCHECK` is defined and passes, but the orchestrator still doesn't restart a clearly hung process inside the container.

If the HEALTHCHECK command itself is hanging or returning success incorrectly (e.g., checking a wrong/unrelated endpoint, or the check process itself getting stuck and timing out in a way that's misinterpreted), the orchestrator never sees a failure signal. Verify the HEALTHCHECK's test command actually exercises the specific failure mode in question, and check `timeout`/`retries` values are tuned so a truly hung check is correctly classified as unhealthy rather than perpetually 'still checking'.