I did learn that there was a BPM action monitor. You can find it from in NWA troubleshooting -> Processes and Tasks -> BPM Actions log.
Actions is used when creating and responding from User tasks and also correlations of messages. They are use on clustered environments to make sure that workloads are distributed evenly among the servers. Normally the setting should make sure there was no queue.
We had a restart of the server that did not go super good so not all locks regarding the BPM framework galaxy.
So when we viewed the BPM Action screen we saw there was 24.000 locks waiting to be processed.
We tried one more restart and that did not remove the locks on the galaxy core. So I removed them form the Java Locks table.
Then in Java properties for the Galaxy Core service I found that if I changed the asyncactionqueue.execution.maxattempts and exec.pool.size with a little and save the changes the galaxy framework was started again.
Now the system is done processing all the tasks in the BPM Action log.