CustomisedConfigurationsHealthCheck failed, the instance showed Johnson page about modifications in setenv.sh. Any request issued to the instance ended with HTTP 503. Meanwhile, querying "/status" endpoint returned "Running" status.
- Modify the HealthCheck to always fail
- See the Johnson page or issue a REST call
- query the "/status" endpoint
When Johnson page is shown and the instance is not working, /status should never return a "RUNNING" state.
I don't think there's a stable workaround. Technically, one could ping an endpoint other than /status, but that would possibly break under other circumstances.