# Workflow storage limits

**URL:** <https://forums.losant.com/t/workflow-storage-limits/1887>\
**Category:** Help\
**Tags:** workflow\
**Created:** [June 14, 2019, 11:29pm UTC](https://forums.losant.com/t/workflow-storage-limits/1887 "2019-06-14T23:29:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cam\_Esdaile](https://avatars.discourse-cdn.com/v4/letter/c/49beb7/32.png) [@Cam\_Esdaile](https://forums.losant.com/u/Cam_Esdaile)\
**Post date:** [June 14, 2019, 11:29pm UTC](https://forums.losant.com/t/workflow-storage-limits/1887/1 "2019-06-14T23:29:22Z")

</div>

Guys, I am trying to understand if there is any technical / practical limits on the number of workflow storage items that can be leveraged in a given workflow. I am making use of the `On Change` node with change identifier to parse to some heavily nested API payloads. Obviously this results in an explosion of storage items as the number of parent objects is parsed + the number of child objects. Any guidance on when this design becomes unmanageable with workflow storage / On Change?

---

<div class="post-metadata">

**Author:** ![Brandon\_Cannaday](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/brandon_cannaday/32/14_2.png) [@Brandon\_Cannaday](https://forums.losant.com/u/Brandon_Cannaday)\
**Post date:** [June 17, 2019, 8:30pm UTC](https://forums.losant.com/t/workflow-storage-limits/1887/2 "2019-06-17T20:30:24Z")

</div>

The Workflow Storage UI (the area that let’s you manage, delete, etc storage keys) will have some difficulty after a few hundred entries, depending on your browser performance. This is purely a front-end consideration and will not impact workflow execution. This would be a fix on our end to add filtering and pagination to that list.

An expected use-case for On Change and Throttle identifiers is a device ID, so the number of keys could get quite large depending on the number of devices reporting data.

As long as your implementation does not create a continuously growing list of unique keys, you should be good to go. In the device ID example, there will only be as many keys as there are devices.

---

<div class="post-metadata">

**Author:** ![Cam\_Esdaile](https://avatars.discourse-cdn.com/v4/letter/c/49beb7/32.png) [@Cam\_Esdaile](https://forums.losant.com/u/Cam_Esdaile)\
**Post date:** [June 20, 2019, 4:55am UTC](https://forums.losant.com/t/workflow-storage-limits/1887/3 "2019-06-20T04:55:37Z")

</div>

Thanks for the guidance on the expected use-case and don’t think the UI pagination / filtering will be a problem for this workflow. Let you know if the device count gets out of hand.