Troubleshoot launch and agent status
Recover from unavailable options, failed provisioning, long transitions, start or stop errors, and cleanup issues.
Cloud lifecycle actions are asynchronous. Wait for either a stable state or an explicit error before trying a competing action.
Launch button is disabled
Check email verification, billing readiness, plan limits, and provider availability. A stopped agent still counts toward an active-agent limit because its disk and record still exist.
If a provider appears but cannot be selected, its control-plane readiness gate is closed. Choose an enabled provider rather than attempting to bypass it.
No locations or machines
Wait for the runtime profile’s location list to finish loading. GPU capacity can be unavailable in a region even when CPU is available. Try auto placement, a different region, any zone, or CPU when the workload does not require GPU.
An empty machine list can also indicate provider permissions or catalog failure. Record the selected provider, profile, region, and visible message.
Provisioning failed
Read Provisioning error on the agent card. Common categories include provider quota, unavailable capacity, image readiness, networking, DNS or certificate setup, and bootstrap failure.
Do not delete the card until you copy the error and agent ID. If the card offers only Delete, use it after collecting evidence so failed state does not occupy the plan limit.
Running but not ready
running confirms provider power state. loading means services are not healthy yet. Initial bootstrap takes longer than a restart. Wait for the health callback rather than opening the URL repeatedly.
If loading persists, record the elapsed time, endpoint, provider state, and any action error. A stop and start is reasonable only after bootstrap should have completed and no provider transition is active.
Start or stop failed
Confirm the card was in a compatible stable state. Refresh once to synchronize provider status. If the error remains, copy Action error and do not send repeated lifecycle requests.
Termination appears stuck
Termination can include VM, disk, firewall, address, DNS, bootstrap-token, and billing-attribution cleanup. Contact support when the card remains terminating or a provider resource persists after the console record disappears. Include the agent ID and provider resource details without credentials.
Your response helps us keep product instructions useful.