[2.0.23] roboport robots are not prioritized for stationing requests

[Quezler]

When a logistic network is really busy there's like no change a roboport's stationing requests are fulfilled.

As you can see on the screenshots this network has plenty of epic logistic robots, plenty of which are sitting in roboports somewhere.

However when trying to request some for stationing it seems that task gets assigned to robots already quite busy, and those will practically never be done.

The expected (or rather, what i wish would actually happen) behavior is that stationing tasks get assigned in this order:
1) airborne robots with no task (and thus already wanting to head to a roboport)
2) matching robots sitting in a roboport
3) airborne robots with a task

Currently stationing requests are "next to useless" in busy networks because of this, therefore it seemed more fitting to file it under bugs than feature requests.

[Muche]

My impression of the situation in your example is that robots are trying to get into the roboport, most of 350 of them are around it waiting to charge up and enter, but instead of entering it they are immediately dispatched to do some nearby job.

So the bot request is succeeding in getting robots to the (busy) location but failing to get them into the roboport.

[Genhis]

I'm marking this as a duplicate of 124287 because it has a developer reply.