Process Instances unprocessed with enabling deployment-aware

Why are you restarting the Camunda Engine after deployment of V2?

When you start the Camunda Engine with deployment aware=true, it will only run those processes that it has on that node. So if you remove V1, restart, and deploy V2, then the engine only knows about V2, and can’t do any work on V1.
Deployment Aware is only needed on heterogeneous clusters. Is there a reason to set it true on your engine?

This Thread is very useful reading on Deployment Aware