Edge runtime lifecycle states

An edge runtime and its instances transition through different states from the moment you start it until they are removed. Each state indicates a different phase or condition of the runtime. These states help administrators understand the current condition of the runtime and take appropriate actions to manage and optimize its operations.

The various transition states of an edge runtime instance are explained in the following table.

Status State Edge runtime (status of edge runtime card on the home page) Edge runtime instances (status of each instance on the Instances Listing page)
Not Applicable Disabled No status is displayed. If the runtime is enabled and then disabled, the status that is displayed is the one before the runtime was disabled. No status is displayed.
Provisioning Enabled Runtime is being provisioned. The runtime pairing is successful and the instance is being set up. You cannot use the runtime to deploy integrations. At least one instance is being provisioned. Other instances are either in Unknown, Offline, or Starting states.
Starting Enabled Runtime is in the process of initializing and preparing to enter the running state. It includes loading configurations and setting up necessary resources. Starting is an intermediate state between Provisioning and Ready states. You cannot use the runtime to deploy integrations. At least one instance is being initialized and is not yet available for operations. Other instances are either in Unknown, Offline, or Provisioning states.

Ready

X Ready

X/Y Ready

Enabled Edge runtime is ready to deploy integrations. and is s in its standard operational state, doing its designated tasks. At least one instance is Ready. If only some instances are running, then the status is displayed as X/Y Ready, where X is the number of instances that are running, and Y is the total number of instances. Other instances are in the Unknown, Offline, Provisioning, or Starting state.
Offline Enabled Edge runtime that has zero instances. The Offline state occurs when registration is initiated but canceled before pairing is completed. You can add an instance and finish the registration, but integrations cannot be deployed until the runtime is in the Ready state. Not Applicable
Syncing Enabled Assets are being synchronized on the edge runtime. Instances are being synchronized to retrieve information of all assets.
Unknown Enabled Instance whose status is not known due to exceptions such as connectivity loss. Any instance that is in an unknown state does not participate in runtime operations at any time. No status is displayed.