It seems like this issue is probably a bug with using the tag() function in an expression transform after a query . But I want to post that we found a work around for anyone else that may come across this issue.
If you create another property on your component, in our case we called it path. You can store the query results in that property and then make use of it in your original property, for some reason this doesn’t cause the flood limit issue even though I would imagine it should be doing the same thing behind the scenes.
