# Event Update Limitation **URL:** \ **Category:** Help\ **Tags:** workflow, events\ **Created:** [January 28, 2026, 12:05am UTC](https://forums.losant.com/t/event-update-limitation/5960 "2026-01-28T00:05:17Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Jason\_Walton](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/jason_walton/32/5023_2.png) [@Jason\_Walton](https://forums.losant.com/u/Jason_Walton)\ **Post date:** [January 28, 2026, 12:05am UTC](https://forums.losant.com/t/event-update-limitation/5960/1 "2026-01-28T00:05:17Z")
Our fielded product updates Losant several times an hour; and in an errored condition, like a failed sensor, I create an event and update its event tage with a ‘number of errored occurrences’. I’ve bumped my head on a ‘maximum number of event updates’ limitation (seen below). Of course the information that creates the event exists in the time-series, but isn’t available ‘at a glance’ when viewing the event itself. ![image](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/e/ed2e24218d6ace232d6cfba2f361c28b18fc1590.png) Is there a recommendation on how to handle this without updating the event? Using a ‘number of occurrences’ tag was convenient, but I assume it comes with some overhead we are trying to avoid. Thanks Team ---
**Author:** ![Dylan\_Schuster](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/dylan_schuster/32/2850_2.png) [@Dylan\_Schuster](https://forums.losant.com/u/Dylan_Schuster)\ **Post date:** [January 28, 2026, 3:14pm UTC](https://forums.losant.com/t/event-update-limitation/5960/2 "2026-01-28T15:14:03Z")
I’m guessing this is an undesirable side effect of our recent changes to also [historically track event tag updates](https://www.losant.com/blog/platform-update-updatable-event-fields-cloud-storage-to-from-edge-device-files). Let me run this case past the engineering team and see what ideas they have - if we can increase that limit, or add an option not to track the tag updates in the array, or something else entirely. ---
**Author:** ![Dylan\_Schuster](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/dylan_schuster/32/2850_2.png) [@Dylan\_Schuster](https://forums.losant.com/u/Dylan_Schuster)\ **Post date:** [January 28, 2026, 4:17pm UTC](https://forums.losant.com/t/event-update-limitation/5960/3 "2026-01-28T16:17:08Z")
I think we’ll handle this by adding a flag on event creation to disable tag update tracking. Hopefully we can get that out in our March release but I can’t promise that quite yet. We discussed doing the flag per event update but that introduces potential “chain of custody” type issues where a user could maliciously update an event without their changes appearing in the log. I will keep you posted. ---
**Author:** ![Jason\_Walton](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/jason_walton/32/5023_2.png) [@Jason\_Walton](https://forums.losant.com/u/Jason_Walton)\ **Post date:** [February 2, 2026, 12:16pm UTC](https://forums.losant.com/t/event-update-limitation/5960/4 "2026-02-02T12:16:56Z")
> [@Dylan\_Schuster](#): > > ussed doing the flag per even I made note of the tracking feature. I really do like the idea of maintaining an auditable log. But this particular aspect of the way I’m using one of the tags probably isn’t audit worthy. Perhaps on Event:Update nodes having an option to participate in the historical tracking might be a fix? ---
**Author:** ![Dylan\_Schuster](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/dylan_schuster/32/2850_2.png) [@Dylan\_Schuster](https://forums.losant.com/u/Dylan_Schuster)\ **Post date:** [March 4, 2026, 3:01pm UTC](https://forums.losant.com/t/event-update-limitation/5960/5 "2026-03-04T15:01:50Z")
We added the flag discussed here in today’s platform update. You can now disable event tag update tracking when creating the event through the UI or the Event: Create Node, which should resolve the “too many updates” issue you were running into. Thanks for bringing this to our attention.