Application Instance Status and Health

Use application instance status and health information to determine whether an instance is running as expected, needs attention, or is still completing a lifecycle step. Run state is the first signal, but admin state, App Update Status, and notifications together give the complete picture.

​

Start from the Applications List

Open Infrastructure > Workloads > Applications. The list shows each instance with its run state, application type, hosting node, source edge app, and project. Use the Status filter to narrow the list to instances in a particular state.

​

Separate the Signals

Run state, admin state, App Update Status, and notifications answer different questions.

​

Interpret Run States

Run states group into three operational categories. For a description of every state, see Application Instance Details.

​

Stable states

The instance is in an expected steady state. The instance requires no action.

​

Transitional states

The instance is moving through a lifecycle step. Wait for it to complete and verify it reaches a stable state. If a transitional state persists beyond a few minutes, check that the hosting node is online and review the node logs. The typical startup sequence for a new instance is: Unprovisioned → Provisioned → Init → Booting → Online. A deployment that includes an image download follows: Unprovisioned → Provisioned → Downloading → Verifying → Loading → Creating Volume → Init → Booting → Online. Other transitional states you might encounter:

​

Attention states

The instance requires investigation.

​

Interpret Admin State

The admin state reflects whether the instance is intentionally started or stopped. It appears as a sub-label below the run state in the Overview tab ribbon and in the State & Timeline card on the Details tab. An instance that is Inactive will not progress to Online even if the hosting node is healthy. If an instance is stuck in a non-Online state and the node is healthy, check the admin state first.

​

Check the App Update Status Signal

The App Update Status signal (Refresh icon button in the detail page toolbar) shows whether the running instance matches its source edge app definition. Open it any time you suspect the instance is running outdated configuration or an older image version. For step-by-step update instructions, see Manage an Application Instance.

​

Review Notifications

The Notifications bell in the instance detail page header shows a color-coded badge when EVE-OS has reported errors, warnings, or notices.

• Red badge: one or more errors are present.
• Amber badge: one or more warnings are present, no errors.
• Blue badge: one or more notices are present, no errors or warnings.

When no notifications are present, the panel shows All clear. Select the bell to view each notification with its severity, explanation, and suggested fix.

​

Readiness Checklist

An application instance is generally ready and healthy when:

• Run state is Online.
• Admin state is Active.
• App Update Status shows no pending updates.
• No errors or warnings appear in the notifications panel.
• Uptime is increasing and Last Seen is recent.
• CPU and memory utilization are within expected ranges on the Overview tab.

​

Troubleshoot by Symptom

​

Next Steps