You are right on this ""- The real issue is why does SAP become unresponsive -"".
It's not happening all the time but just randomly so we can't predict why that is happening(not a large table), if we re-run request, then it works, so maybe it's something in SAP side that should be covered so it is at least timing out (not the case, it is stuck forever, +5 hours).
You gave me a good idea with the Command line workaround. I think that might work, because we can create a bat file launching that process that is just going to click execute, so the initial process will go further to the wait stage until the expected result is there.
One question, doing that the ""Resource will not be too busy to run the second process"", right? I don't know what happens if the resource is already running the first process.
Thanks a lot for your ideas.
Ismael.