# DEV-"Error timed out waiting to be healthy" message on using -i even when deployments gets healthy.
## What happened
Issue astronomer/astro-cli#1189 (closed, 6 comments): The following command created deployment under a shared hosted cluster and showed the error message "Error timed out waiting to be healthy" even when the deployment gets healthy. ``` shrividyahegde@Shrividyas-MacBook-Pro Downloads % ./astro deployment create -n test111 -p gcp --dag-deploy enable -e CeleryExecutor -v 8.0.0 -a enable --region us-central1 --scheduler-size small -i Current Workspace: Hosted workspace Waiting for the deployment to become healthy… This may take a few minutes NAME NAMESPACE CLUSTER DEPLOYMENT ID RUNTIME VERSION DAG DEPLOY ENABLED test111 weightless-sky-4315 N/A...
## What works
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.
## Caveats
This comes from one real issue thread (gh:astronomer/astro-cli#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.