Workflow storage limits

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?