CLI deploy wait timeouts show last job status

August 30, 2026 · release

@voicethere/cli 0.12.8

@voicethere/cli 0.12.8 makes deploy --wait timeouts easier to diagnose.

If the wait window expires before rollout finishes, the error includes the last observed job status:

Timed out after 600000ms waiting for deployment <id> (last status=queued)

queued means the control plane has not started the rollout yet (often busy with other projects). active means Helm is still running. none means no poll completed.

A Helm failure still marks the job failed before the client timeout — that path is unchanged.

Try it

npm install -g @voicethere/[email protected]
voicethere deploy --wait

Similar posts

← All posts