Processes running in parallel run forever

We currently have 195 AD projects with cross applications. If I do a make build for a maximum of 25 projects in parallel, then it very often happens that the builds abort with the following error:
"========================== =
BATCH MAKE ERROR FILE
============================

Unable to perform the operation!
The project is temporarily locked by a locker without session.
Please, try again later! "
So that parallel builds should be possible, I see only one JMCobol or ADASM service running for hours.
What is inexplicable to me now, why a make takes several hours to change a file. Furthermore, why does the process generate a BatchError file even though the task appears to be processed further asynchronously in the background?
It is difficult for me to see the end of a make. What I have been relying on so far is the creation of the update or batch file. If an update file says "Process completed", then I do the post-processing. If a batch error file is created then there is no post processing and the process will restart after 5 to 10 minutes.
The new process will then probably break off again because the previous one is still running.
At the moment I only see a chance via the Sever.log or Status.log, because unfortunately the tasks do not provide any information about their processing either.
Due to loops in the analysis and the associated long-running make / builds, the automated process must be switched back to manual.