When trying to publish any changes made to your configuration, you might be presented with some warnings if any incorrect configuration is detected. This article will explain the possible error messages you can see, and how to remedy them.



Ordinarily, you will see the below prompt to Publish your configuration changes


In this instance, you can go ahead and publish your changes.




However, on some occasions you may see the following warnings;


An Alert type is enabled but not usable by any Group




This rule ensures that all enabled Alert Types are assigned to at least one Group, preventing unnecessary Alert Types from being enabled. When an Alert Type is not allowed by any Group, it is expected to be disabled instead.


Solution: The alert type in question should be disabled, or assigned to one or more groups.




A Group is being targeted twice in the same escalation



All Groups is being targeted twice in the same escalation



Ungrouped Locations is being targeted twice in the same escalation




These rules enforce the singular use of any given Group across all Escalation Levels of a given Escalation Path. When a Group has already received the Alert, it can not receive the Alert again


Solution: Ensure that the specified group(s) is only set to receive an alert once. 




An Escalation Level has no targets




The affected Group has no escalation levels set, or an escalation level has become empty following the deletion of the targeted group.


Solution: Edit the escalation to ensure there is at least one designated escalation level.




An escalation level is targeting a Group that has already been targeted by All Groups




This rule prevents redundant Escalation Levels that target Groups after All Groups has already been targeted, since all Groups would have already received the Alert. When a Group has already received the Alert, it can not receive the Alert again 


Solution: Edit the escalation paths accordingly.




 A Group with GPS disabled has no Locations




This rule ensures that Groups which disallow GPS/geocoded Locations have at least one fixed Location defined.  


Solution: Devices that can not provide their Location via GPS need at least 1 Location available to select 




A Group with 0 Locations has non-mobile Devices




Non mobile (Windows) devices must have at least one Location assigned, since non-mobile Devices require a fixed Location.


Solution: Ensure that all groups that have non mobile devices have at least 1 Location available to select.




A Group has no Escalation Levels




All groups must have at least one Escalation level configured to handle alert delivery.


Solution: Ensure all groups are configured with an escalation level




A Device is prompting it's user to select from a single Location




This rule prevents Devices that are configured as movable from having only a single location.


Solution: If a Device is set to "Prompt for Location" ensure that more than one Location is assigned to that device.