# \[Feature\] Add start/endDate keyword args to system.alarm.queryStatus

**URL:** <https://forum.inductiveautomation.com/t/feature-add-start-enddate-keyword-args-to-system-alarm-querystatus/54792>\
**Category:** Ignition\
**Created:** [January 8, 2022, 12:00am UTC](https://forum.inductiveautomation.com/t/feature-add-start-enddate-keyword-args-to-system-alarm-querystatus/54792 "2022-01-08T00:00:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dustin.cooper](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dustin.cooper/32/29963_2.png) [@dustin.cooper](https://forum.inductiveautomation.com/u/dustin.cooper)\
**Post date:** [January 8, 2022, 12:00am UTC](https://forum.inductiveautomation.com/t/feature-add-start-enddate-keyword-args-to-system-alarm-querystatus/54792/1 "2022-01-08T00:00:07Z")

</div>

Idea post [here](https://inductiveautomation.canny.io/ignition-features-and-ideas/p/add-startdateenddate-as-params-to-systemalarmquerystatus)

I would like to be able to limit the size (and increase the performance of) this query function when run in a gateway script by limiting the time range, the same way that we can with the `system.alarm.queryJournal` function.

I have tried using the `any_properties` keyword with the `EventTime` key, but because the PyAlarmEvent treats this as a string, only the `=` and `!=` operators are allowed.

Ideally, I would like to be able to query results for ALL alarm states during a given time range, but only active alarms (for the edge case that an alarm stays active for hours/days at a time).