We upgraded Clarity from 15.6.1 to 16.0.1 and the pre-upgrade processes on the system are not moving forward. They are not being loaded on the process engine either. Any new process created after the upgrade works OK.
The process engine does not recognise the processes at DB side as per the hostname change action which typically results during a DB refresh (prod to non-prod)
Steps to resolve/workaround the issue:
SQL query to differentiate process engine ids for the processes that are in running state:
select process_engine_id, count (*) from bpm_run_processes where status_code='BPM PIS RUNNING' group by process_engine_id