It’s been a while since I looked at the logic in the Task Controller, so others would know best. And I am not sure if it was only meant for Feed and Need type tasks.
What I remember is tasks have to queue and buffer for a bit before the prioritization goes into effect and this is dependent on when a station (WP) sends the task request to the controller.
The Task Controller checks if the request is prioritized. If yes, the request is added to a list, for instance a priority feed list of requests. Of course, the first time the Task Controller gets a task request, those priority lists are empty, so the first task request is executed if possible.
Is the expected outcome the Human worker does the task at Works Process #13 when all of the other three stations are queuing? Unfortunately, I cannot help atm, but try setting the resource allocation property of the Task Controller to Least Utilized or something to that effect. Not sure if that property overrides the priority list.
@Ockema and @kbqhs are you able to make it work now?
@jouha With the second case of “HumanProcess:Works Process #4” does that happen in the beginning of simulation or after some time?
If the HumanProcess task from station 1 is received first, the Task Controller knows to wait or by the time it does number 2 in its logic, the task from station 4 would have already been received, thereby the resource is assigned the task at station 4?