Astro Platform is live. Nova is available by request. Start free
Troubleshoot
When an application is not Running, AstroPulse says why on its page: a status reason, its events and its logs. Read them in that order, then find the message below for its cause and fix. Ask Nova on the application's page reads the same signals and says the likely cause.
Open the application from Workloads > Applications. When it is not running, the Overview shows the status reason, with See events and See logs.
Select Events. Deployment Events are AstroPulse's view of the deploy; Kubernetes Events are the cluster's (scheduling, image pulls, probes); Platform Events are the platform's own. Select Connect to stream new events. A Warning row usually names the cause.
Open zoom view
Select Logs, then Start streaming, and pick a pod and a container. For a container that keeps restarting, open Stream Settings and set Previous: ON to read the run that crashed.
Open zoom view
Find the message below. When the specification is right but the cluster drifted from it, select Resync in the header: it reapplies only the resources that drifted, and the application keeps serving.
The application's page shows Running. While a new version deploys, the Overview says which version is serving, for example "Deploying v5; v4 keeps serving until it's ready."
A FailedScheduling warning in Kubernetes Events, such as "0/6 nodes are available: 1 Insufficient cpu, 1 Insufficient memory…"
Cause
No node has room for the pods' requests.
Fix
Add nodes or a node group, or turn on node autoscaling. An image application's requests come from its availability tier; a chart's or manifest's from its own values.
"The previous copy of this application's namespace is still being deleted. It deploys when that finishes."
Cause
The application was deleted and deployed again before its old namespace was gone.
The cluster refused the rendered resources. The rest of the message is the cluster's reason.
Fix
Fix the chart, manifest or setting it names, and apply again.
"Application <app> already has a deployment in progress. Use --force to terminate it and start a new sync."
Cause
A resync was asked for while a sync is still running.
Fix
Wait for it, or run astroctl app resync <app> --force for a sync that is itself stuck. It stops the sync in progress and reapplies every resource, never deleting and recreating.
"That update was not applied, so <version> keeps serving: …"
Cause
The last update failed; the earlier version is still running.
Fix
Read the reason after the colon, fix it, and apply again, or roll back.
If the application was healthy before the last deploy, roll back to the previous good version while you investigate: its History tab, Roll back. See Releases and rollback.
Nova: ask it, for example "why is hello-world unhealthy?" or "show me the errors in hello-world's logs". It can also run a deeper cluster diagnosis when the cause is the cluster.
SDK and API: the same operations, in the API reference.
astroctl app logs hello-world # logs across all pods, follows by default
astroctl app resync hello-world # reapply only what drifted
servingNote says which version is serving and why, when it is not the one you last applied, and is empty when they match. A watch ends with "The watch stopped: the connection to AstroPulse closed." when the connection closes; nothing failed, run the command again. Every flag: astroctl app.