system.alarm.queryStatus results order

It looks like system.alarm.queryStatus returns the results with the highest priority last. I have tested this several times and it always seems to be this way. Is this simply coincidence, or how it is? If it is, this is great as I wanted an easy way to grab the highest priority from a group of alarms/tag paths.

I wouldn’t rely on this, it looks like an implementation detail/quirk that depends on the query strategy chosen by Ignition, which depends on the nature of your query.

Perfect, thank you for the response.