# Defined alarms in the system **URL:** \ **Category:** Ignition\ **Created:** [September 15, 2020, 3:52pm UTC](https://forum.inductiveautomation.com/t/defined-alarms-in-the-system/38696 "2020-09-15T15:52:24Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [September 16, 2020, 12:55pm UTC](https://forum.inductiveautomation.com/t/defined-alarms-in-the-system/38696/5 "2020-09-16T12:55:56Z")
> [@Best way to generate an alarm list](http://forum.inductiveautomation.com/t/best-way-to-generate-an-alarm-list/11773/4): > > Sorry all… but, I’ve tried to use the queryStatus above to get a list of all alarms, however I only get 27 alarms returned, where there should be hundreds. I ran this in two locations: my local dev environment, no connection to PLCs where I got the 27 alarms; I also ran it on the production gateway where it returned a large number of alarms. I’m now not confident the “full” alarm list that I gave the customer using this function is in fact a full list at all… Why would these results be differen… I found that using statusquery didn't get a full list. I don't think I ever was able to get a full list... Or maybe I had to use system.tag.browse for it or the other config one? --- _[View the full topic](https://forum.inductiveautomation.com/t/defined-alarms-in-the-system/38696)._