# Ignition garbage collector behavior changed at the same time as a tag re-evaluation caused a problem

**URL:** <https://forum.inductiveautomation.com/t/ignition-garbage-collector-behavior-changed-at-the-same-time-as-a-tag-re-evaluation-caused-a-problem/88687>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [April 11, 2024, 1:00pm UTC](https://forum.inductiveautomation.com/t/ignition-garbage-collector-behavior-changed-at-the-same-time-as-a-tag-re-evaluation-caused-a-problem/88687 "2024-04-11T13:00:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bmeyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmeyers/32/37453_2.png) [@bmeyers](https://forum.inductiveautomation.com/u/bmeyers)\
**Post date:** [April 11, 2024, 1:00pm UTC](https://forum.inductiveautomation.com/t/ignition-garbage-collector-behavior-changed-at-the-same-time-as-a-tag-re-evaluation-caused-a-problem/88687/1 "2024-04-11T13:00:55Z")

</div>

Ignition version 8.1.17

At approximately 11:05 am yesterday one of our gateway tags re-evaluated itself when it shouldn't have. This caused a change script to execute and reset a daily counter (typically gets reset at midnight).

What I find interesting is in the gateway there were no errors and the garbage collector behavior also changed at that time.

 ![dddss](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/e/4ec36e8cb58f53aab605fb70fb5e09339dbedc13.png)

Any idea about where I should investigate further? What would cause this behavior change?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [April 11, 2024, 1:53pm UTC](https://forum.inductiveautomation.com/t/ignition-garbage-collector-behavior-changed-at-the-same-time-as-a-tag-re-evaluation-caused-a-problem/88687/2 "2024-04-11T13:53:53Z")

</div>

Your memory usage pattern **improved**. I don't see a problem with that.

Your use of a tag change script to trigger counter resets seems fragile out of the box. If you want something to happen on a schedule, use a scheduled event script. Or for older versions without that, use a timer event that checks a "last run timestamp" memory tag to determine when it should execute the rest of its logic.

Even better is to not reset counters at all, but use regularly-recorded odometer-style counters.