# TagHistoryQueryParams aggregation mode now required in Ignition 8.3.4? **URL:** \ **Category:** Module Development\ **Created:** [March 7, 2026, 4:35pm UTC](https://forum.inductiveautomation.com/t/taghistoryqueryparams-aggregation-mode-now-required-in-ignition-8-3-4/114377 "2026-03-07T16:35:58Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![mpderbec](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@mpderbec](https://forum.inductiveautomation.com/u/mpderbec)\ **Post date:** [March 7, 2026, 4:35pm UTC](https://forum.inductiveautomation.com/t/taghistoryqueryparams-aggregation-mode-now-required-in-ignition-8-3-4/114377/1 "2026-03-07T16:35:58Z")
Something changed between Ignition 8.3.0 and 8.3.4 such that the AggregationModes passed by TagHistoryQueryParams to TagHistoryManager.queryHistory() can no longer be null (an exception is thrown now). I don’t want any aggregation, I just want raw data, so I tried passing in an empty list. An exception is no longer thrown, but now a weird data point is returned that is in the future. It seems like maybe it’s the last value? But it has a future timestamp, roughly eight hours into the future. Maybe a timezone weirdness? Anyone have any idea what this is? Is there a proper way to specify that you do not want any aggregation to be done? The history provider in this case is Core Historian. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/c/9c0fe17324b213cd9c9108e6cf94374d485021e6.png) ---
**Author:** ![mpderbec](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@mpderbec](https://forum.inductiveautomation.com/u/mpderbec)\ **Post date:** [March 20, 2026, 11:05pm UTC](https://forum.inductiveautomation.com/t/taghistoryqueryparams-aggregation-mode-now-required-in-ignition-8-3-4/114377/2 "2026-03-20T23:05:10Z")
Forgot to say: I verified that the same code (i.e., an empty AggregationModes list) running under 8.3.0 does not produce the anomalous value at the end. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [March 20, 2026, 11:19pm UTC](https://forum.inductiveautomation.com/t/taghistoryqueryparams-aggregation-mode-now-required-in-ignition-8-3-4/114377/3 "2026-03-20T23:19:16Z")
What issue are you getting when you pass null? Javadocs on `TagHistoryQueryParams` suggest it should be allowed: ```python /** * If not null, must be 1-to-1 list corresponding to tag paths, specifying the aggregation mode * for the column. If the list is null, or a particular entry is null, the general aggregation * mode will be used instead. */ List getColumnAggregationModes(); ``` ---
**Author:** ![mpderbec](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@mpderbec](https://forum.inductiveautomation.com/u/mpderbec)\ **Post date:** [March 20, 2026, 11:49pm UTC](https://forum.inductiveautomation.com/t/taghistoryqueryparams-aggregation-mode-now-required-in-ignition-8-3-4/114377/4 "2026-03-20T23:49:48Z")
Here are my query params (without specifying AggregationModes) ```python BasicTagHistoryQueryParams queryParams = BasicTagHistoryQueryParams.newBuilder() .paths(tagPathList) .startDate(startDate) .endDate(endDate) .queryFlags(Flags.of( TagHistoryQueryFlags.BOUNDING_VALUES_YES, TagHistoryQueryFlags.NO_INTERPOLATION, TagHistoryQueryFlags.NO_PREPROCESSED_DATA )) .returnSize(0) .returnFormat(ReturnFormat.Tall) .build(); ``` and here’s the exception: ```python jvm 1 | java.lang.NullPointerException: Cannot invoke "java.util.List.isEmpty()" because the return value of "com.inductiveautomation.ignition.common.sqltags.history.TagHistoryQueryParams.getColumnAggregationModes()" is null jvm 1 | at com.inductiveautomation.historian.gateway.query.writing.HistoryWriter.hasNoAggregation(HistoryWriter.java:183) jvm 1 | at com.inductiveautomation.historian.gateway.query.writing.HistoryWriter.calculateBlockSize(HistoryWriter.java:194) jvm 1 | at com.inductiveautomation.historian.gateway.query.writing.HistoryWriter.(HistoryWriter.java:82) jvm 1 | at com.inductiveautomation.historian.gateway.query.writing.TallHistoryWriter.(TallHistoryWriter.java:16) jvm 1 | at com.inductiveautomation.historian.gateway.HistorianManagerImpl.createHistoryWriter(HistorianManagerImpl.java:1776) jvm 1 | at com.inductiveautomation.historian.gateway.HistorianManagerImpl.queryHistory(HistorianManagerImpl.java:1083) jvm 1 | at com.inductiveautomation.ignition.gateway.sqltags.history.TagHistoryManagerBridge.queryHistory(TagHistoryManagerBridge.java:99) jvm 1 | at com.seeq.ignition.v83.gateway.link.IgnitionGatewayConnection.getSamplesViaTagHistoryManager(IgnitionGatewayConnection.java:1539) jvm 1 | at com.seeq.ignition.v83.gateway.link.IgnitionGatewayConnection.getSamples(IgnitionGatewayConnection.java:1604) jvm 1 | at com.seeq.link.sdk.DatasourceConnectionV2Host.signalRequest(DatasourceConnectionV2Host.java:1790) jvm 1 | at com.seeq.link.sdk.BaseDatasourceConnection.processMessage(BaseDatasourceConnection.java:492) jvm 1 | at com.seeq.link.sdk.BaseDatasourceConnection.lambda$processMessage$2(BaseDatasourceConnection.java:425) jvm 1 | at com.seeq.link.sdk.BaseDatasourceConnection.lambda$processMessage$0(BaseDatasourceConnection.java:417) jvm 1 | at com.seeq.link.sdk.utilities.DefaultConcurrentRequestsHandler.lambda$runWhenPermitted$0(DefaultConcurrentRequestsHandler.java:71) jvm 1 | at com.seeq.link.sdk.utilities.ThreadCollection$Worker.run(ThreadCollection.java:313) jvm 1 | at com.seeq.link.sdk.utilities.ThreadCollection.lambda$spawn$2(ThreadCollection.java:170) jvm 1 | at java.base/java.lang.Thread.run(Unknown Source) ``` ---
**Author:** ![mpderbec](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@mpderbec](https://forum.inductiveautomation.com/u/mpderbec)\ **Post date:** [March 20, 2026, 11:52pm UTC](https://forum.inductiveautomation.com/t/taghistoryqueryparams-aggregation-mode-now-required-in-ignition-8-3-4/114377/5 "2026-03-20T23:52:25Z")
Explicitly specifying `null` has the same effect. E.g. ```python BasicTagHistoryQueryParams queryParams = BasicTagHistoryQueryParams.newBuilder() .paths(tagPathList) .startDate(startDate) .endDate(endDate) .queryFlags(Flags.of( TagHistoryQueryFlags.BOUNDING_VALUES_YES, TagHistoryQueryFlags.NO_INTERPOLATION, TagHistoryQueryFlags.NO_PREPROCESSED_DATA )) .aggregationModes(null) .returnSize(0) .returnFormat(ReturnFormat.Tall) .build(); ``` ---
**Author:** ![mpderbec](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@mpderbec](https://forum.inductiveautomation.com/u/mpderbec)\ **Post date:** [March 20, 2026, 11:54pm UTC](https://forum.inductiveautomation.com/t/taghistoryqueryparams-aggregation-mode-now-required-in-ignition-8-3-4/114377/6 "2026-03-20T23:54:29Z")
I’ll mention that the stack trace shows Ignition calling a `hasNoAggregation()` function, which tries to look if the list is empty. That’s why I tried handing in an empty list, which seems to be what it wants. The problem now is that there is an anomalous value returned as the final sample, as described in the original post. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [March 23, 2026, 5:53pm UTC](https://forum.inductiveautomation.com/t/taghistoryqueryparams-aggregation-mode-now-required-in-ignition-8-3-4/114377/7 "2026-03-23T17:53:04Z")
Yeah, the NPE is just a bug where we're not being sufficiently defensive. I'm not sure what's going on with the anomalous result but I'll point the history team at this thread and see if they can explain what's going on. ---
**Author:** ![Kurt.Larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kurt.larson/32/6426_2.png) [@Kurt.Larson](https://forum.inductiveautomation.com/u/Kurt.Larson)\ **Post date:** [March 24, 2026, 3:28am UTC](https://forum.inductiveautomation.com/t/taghistoryqueryparams-aggregation-mode-now-required-in-ignition-8-3-4/114377/8 "2026-03-24T03:28:12Z")
Following up, that added post value should be removed as of the 8.3.5 nightlies. ---
**Author:** ![mpderbec](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@mpderbec](https://forum.inductiveautomation.com/u/mpderbec)\ **Post date:** [March 24, 2026, 3:40pm UTC](https://forum.inductiveautomation.com/t/taghistoryqueryparams-aggregation-mode-now-required-in-ignition-8-3-4/114377/9 "2026-03-24T15:40:20Z")
@Kurt.Larson – I confirmed that the current 8.3.5 nightly no longer has the anomalous value. Thank you!