> ## Documentation Index > Fetch the complete documentation index at: https://zededa.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL. > Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other. > Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking. > Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify. # Application Instance Status and Health > Interpret application instance run states, admin state, App Update Status, and health signals in Edge Infrastructure Services. 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. | Signal | What it tells you | Where to check | | - | - | - | | Run state | The current operational condition of the instance as reported by EVE-OS (Edge Virtualization Engine). | Applications list and instance detail page header | | Admin state | Whether the instance is intentionally active or deactivated. | Instance detail **Overview** tab ribbon and **Details** tab | | App Update Status | Whether the running instance matches its source edge app definition. | **Refresh** icon button in the instance detail page toolbar | | Notifications | Errors, warnings, and notices reported by EVE-OS for the instance. | Notifications bell in the detail page header | | Uptime and Last Seen | Whether the instance is actively reporting runtime data. | Instance detail **Overview** tab ribbon | ## Interpret Run States Run states group into three operational categories. For a description of every state, see [Application Instance Details](https://zededa.mintlify.site/new-ui/infrastructure-services/applications/app-instance-details.md#run-states). ### Stable states The instance is in an expected steady state. The instance requires no action. | State | Meaning | | - | - | | Online | The instance is running and reporting normally. | | Halted | The instance has been stopped. It remains on the node and can be restarted. | | Powered Off | The instance has been powered off. | | Maintenance Mode | The instance is in maintenance mode. | ### 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: | State | What is happening | | - | - | | Delayed Start | The instance is waiting for its configured staggered start delay (the interval that spreads startup times across multiple instances on shared infrastructure) before booting. | | Halting | The instance is stopping. | | Rebooting | The instance is rebooting. | | Restarting | The instance is restarting. | | Updating | The instance is applying a configuration or image update. | | Purging | The instance is being purged before a clean re-deployment. | | Preparing Power Off | EVE-OS is preparing the instance for power off. Applies to Virtual Machine instances. | | Powering Off | The instance is in the process of powering off. Applies to Virtual Machine instances. | | Prepared Power Off | The instance has completed power-off preparation and is waiting to power off. Applies to Virtual Machine instances. | ### Attention states The instance requires investigation. | State | Usual first check | | - | - | | Error | Open notifications for the error message. Check **Infrastructure > Monitor > Logs** filtered to this instance. Verify that the hosting node is online. | | Suspect | Open notifications and review recent events. Check the hosting node's status and logs. | | Offline | Verify that the hosting node is online and reachable. Check the node's network connectivity. | | Unknown | Confirm the hosting node is online. Wait for the next state report, then check logs if the state does not update. | ## 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. | Admin state | Meaning | | - | - | | Active | The instance is started. EVE-OS will attempt to bring it to **Online**. | | Inactive | The instance is deactivated. EVE-OS keeps it stopped regardless of run state. | 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. | Signal | Meaning | Action | | - | - | - | | Up to date | The instance matches its source edge app. | No action needed. | | Update available | A newer version of the source edge app is available. The panel shows the current and target versions and a configuration diff. | Apply the update using **Reactivate** or **Update** from the Actions menu. | | Purge and update required | The source edge app has changed in a way that requires a clean re-deployment. | Apply the update using **Purge & Update** from the Actions menu. Review the configuration diff and consider creating a snapshot first. | For step-by-step update instructions, see [Manage an Application Instance](https://zededa.mintlify.site/new-ui/infrastructure-services/applications/manage-an-application-instance.md#app-update-status). ## 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 | Symptom | What to check first | | - | - | | Instance is **Error** | Open notifications for the error message. Check **Infrastructure > Monitor > Logs** filtered to this instance. Verify that the hosting node is online and healthy. | | Instance is **Suspect** | Open notifications and review recent events on the **Overview** tab. Check the hosting node's status. | | Instance is **Offline** | Verify that the hosting node is online. Check the node's network adapters and connectivity. | | Instance is stuck in a transitional state | Verify that the hosting node is online. Check **Infrastructure > Monitor > Logs** for errors during the transition. | | Instance is **Halted** and should not be | Check the admin state. If admin state is **Inactive**, start the instance from the Actions menu. | | Instance is **Online** but the application is not working | Check CPU and memory utilization on the **Overview** tab. Review the **Interfaces** tab for network connectivity. Check **Infrastructure > Monitor > Logs** for application-level errors. | | App Update Status shows a pending update | Open the App Update Status panel to review the configuration diff. Apply the appropriate update action from the Actions menu. | | Notifications show a recurring error | Note the error explanation and suggested fix in the notifications panel. If the error persists after following the suggested fix, check the hosting node's logs and status. | ## Next Steps > [card] [Application Instance Details](https://zededa.mintlify.site/new-ui/infrastructure-services/applications/app-instance-details.md) > > The full run states table and a reference of all detail page tabs and fields. > [card] [Manage an Application Instance](https://zededa.mintlify.site/new-ui/infrastructure-services/applications/manage-an-application-instance.md) > > Take lifecycle actions such as activate, restart, update, and purge. > [card] [Node status and health](https://zededa.mintlify.site/new-ui/infrastructure-services/nodes/node-status-and-health.md) > > Interpret the health of the hosting node. > [card] [Monitor Logs](https://zededa.mintlify.site/new-ui/infrastructure-services/monitoring-logs-events-reports-jobs.md) > > View application logs filtered to this instance.