Deviations
Identifying and resolving service resources that fail to reach their target states.
Last updated
Was this helpful?
Identifying and resolving service resources that fail to reach their target states.
Last updated
Was this helpful?
A deviation occurs when a service resource fails to reach its target state after the service is enabled. When you , its resources should transition from disabled to enabled (or to another specified target state defined in the service commissioning file). The service commissioning file contains detailed specifications of all resources and their required states for proper service functionality.
However, various issues (such as hardware failures, network problems, or configuration errors) can prevent resources from achieving their intended states. When this happens, the affected service is marked as deviated.
Cybus Connectware provides multiple ways to identify and investigate deviations:
When a deviation occurs, a pop-up notification appears in the Admin UI. This notification provides an immediate alert that one or more services are not functioning as expected.
To view all deviated services, click the down arrow in the notification panel. This expands the list to show all services currently experiencing deviations.
Deviation status is also displayed in multiple locations throughout the Admin UI:
When you click on a deviation warning message, the system displays a detailed list of resources whose actual states differ from their expected states:
For a comprehensive analysis of which specific resources are causing the deviation:
Click on the deviated service name in the services list
Navigate to the Deviations tab for that service
Review the detailed comparison between expected and actual states for each resource
When addressing deviations, focus on:
Identifying the root cause (hardware, network, configuration)
Resolving the underlying issue
In the
Within the for individual services
In lists for affected services
Re-enabling the service to verify the resolution. See .