## TL;DR

For "Error timed out waiting to be healthy": check your version of Astronomer first , maintainers often fix the underlying bug in a later release, and the thread may predate it.

```text
Error timed out waiting to be healthy
```

## Steps

1. If `astro deployment create -i` prints 'Error timed out waiting to be healthy' even though the deployment actually becomes healthy, ignore the message: it is a CLI polling bug, not a failed deployment. The team shipped the workaround in the astro CLI release the following week and the reporter retested it resolved; upgrade the astro CLI and the false timeout goes away.

2. This comes from one real issue thread (https://github.com/astronomer/astro-cli/issues/1189); it is the verified fix or approach from that thread, not a general manual. Check your version of Astronomer first , maintainers often fix the underlying bug in a later release, and the thread may predate it.

## When to use

You are seeing this: If astro deployment create -i prints 'Error timed out waiting to be healthy' even though the deployment actually becomes healthy, ignore the message: it is a CLI polling bug, not a failed deployment. Use this skill when you run into "DEV-"Error timed out waiting to be healthy" message on using -i even when deployments gets healthy".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: -v 8.0.0. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

## Sources

- https://github.com/astronomer/astro-cli/issues/1189