I see. When move inventory with confirm. after complete move inventory
=> switch move inventory to in progress, make new move confirm
At moment user detect error at move inventory. He only do a void move inventory document.
but move confirm document is not void. receiver must complete move confirm.
I think can improve by also void move confirm with void move inventory.
Triaged, the issue is not reproducible as described but found more problems.
Because of - when trying to void the inventory move the user sees an error:
Could not save changes: : Open: Move Confirm
Which is good, it forces the user to go first to the confirmation and void it.
But there I found the movement confirm cannot be void, the code was not prepared for that, and if cannot be void, then the inventory move cannot be modified or voided also, so the system becomes stuck with those two docs.
Implemented the void move confirm with pull request 227