> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/troubleshooting-and-resources/armory/general/instance-is-not-healthy-but-the-deployment-shows-as-succeeded.md).

# Instance is not healthy but the deployment shows as succeeded

### Issue <a href="#issue" id="issue"></a>

In an ECS deployment, the UI shows "successfully deployed" but fails health-check fail 5 seconds later. Health checks are fail but the application still shows as being deployed.The following stage for example is being utilized:

```
  "completeOtherBranchesThenFail": true,
  "dependsOn": [],
  "executionOptions": {
    "successful": true
  },
  "failPipeline": false,
  "name": "Deploy app Stack [dev, ........",
  "stageTimeoutMs": 900000,
  "type": "deploy"
}
```

The pipeline completes as succeeded but in the `server group logs` there are messages for `failures` (service unhealthy).

### Cause <a href="#cause" id="cause"></a>

Ideally, the deployment should only succeed if the underlying service/task is healthy. This issue is currently being investigated further by Armory Engineering.