Version: 2.0.76 (build 84451, expansion, win64)
Platform: Windows 64-bit
What: Roboport logistic requests only recall the first robot in a logistic group
What I did:
I configured logistic requests in the roboports to recall logistic robots from my network for replacement. The requests are organized into logistic groups, each containing multiple robot entries. I have been running this setup for roughly 300 hours of gameplay, and the network has been stuck at ~10,000 robots that I cannot remove.
What happened:
Only the first robot entry in a logistic group is ever recalled. Every subsequent entry in the same group is ignored, even when the first entry's slot is empty (i.e., the first request has already been satisfied, / that all robots have been recalled from the network).
The two attached screenshots (post1.png, post2.png) show this on
two adjacent roboports.
What I expected:
All robot entries in a logistic group should be recalled in turn or all at once, much like any logistics group. Once the first request is satisfied, subsequent entries in the same group should continue to be requested until they are satisfied as well.
Frequency:
Robots stopped siphoning from the network, and the issue has persisted since.
Attachments:
- factorio-current.log
- save file
- post1.png
- post2.png
[2.0.76] Roboport logistic requests only recall the first robot in a logistic group
-
mr00anderson
- Burner Inserter

- Posts: 8
- Joined: Thu Mar 12, 2026 5:57 pm
- Contact:
[2.0.76] Roboport logistic requests only recall the first robot in a logistic group
- Attachments
-
- factorio-current.log
- (42.08 KiB) Downloaded 13 times
-
- The Long Game Nauvis - Base Clean Stone Expansion.zip
- (114.62 MiB) Downloaded 12 times
-
mr00anderson
- Burner Inserter

- Posts: 8
- Joined: Thu Mar 12, 2026 5:57 pm
- Contact:
Re: [2.0.76] Roboport logistic requests only recall the first robot in a logistic group
Missed that. Thank you. Although this is all very confusing if you don't know where to dig into that. I spent a long time trying to remove drones using methods all too familiar; I could have done it within an hour, not 300. R.I.P Time.
