Hello,

We just recently upgraded our environment from 10.3.1 to 10.4.5. During the testing phase of the upgrade we noticed a number of already completed instances seemed to have been "reactivated". One process in particular has some timer events that trigger activities and that event is what "reactivated". So now we have about 200 instances in progress that have already been completed and assigned to staff (Some of which are no longer even employed her). We were told that this happened likely due to the routing service restarting during the upgrade. But this doesn't make sense to us in the case of the already completed instances, especially since we have manually restarted  ( to relieve memory spikes) the routing service on several occasions and not seen this happen.

Has anyone ever experienced this while doing an upgrade? If so, were you able to determine what actually is the reason why this happened? We are concerned because sooner than later we will be discussing upgrading to v.11 and do not want to have to cancel all these instances again during that time .