martin@rootjazz wrote:The problem is, you would, others wouldn't.
The reason it is all in one action is that if you have lots of accounts, then it is going to clog up the processor view and stop other actions running while they all run.
In that case, it's very selective. Everything else is single processes. Now, if any account fails to upload, I have to dive into that process and find the failed logins one by one...to see what the problem is with them.
One way or another, you are using multiple threads for that action. The only difference is that you have x number of more process in your processing few. But that is easily solved by sorting on actions. There is no way to sort anything if you have to find something in a process with x number of completed actions that either failed or succeded.