why do subscriptions change an insert/remove action to a move action

Summary:

I intentionally did an insert/remove action on my request to account for odd behaviors in alternate hierarchies and to prevent impacting the value in other hierarchies.

My value needed to exists across 3 different trees with similar parents in some trees and a unique parent in the 3rd. I was removing the value from the unique parent in my 3rd tree and adding it to a different unique parent.

When the subscription ran, it converted the action to a move. And then it failed to process the action with the error "Row skipped because the move action would result in an invalid hierarchy structure with the node as a descendant or sibling of itself."