Reason: A very common construction is an inserter hooked up to the logistics network (pulling from a train or assembler into a provider chest) which either activates or sets filters depending on the contents on the logistics network. e.g., "Pull repair packs out of cargo wagon if logistics network has repair pack < 200" or "pull express belt out of assembler if logistics network has express belt < 500". I personally like to insert these items into active providers such that the items are then relocated to a central storage location. Unfortunately, while items in the active provider count as being in the logistics network, items *after* they are picked up by the bot but *before* they are deposited in the storage chests do not count as being in the logistics network. This means that I always end up with more items than I want in the logistics network, depending on bot travel time.
e.g.: I want 50 turrets, but currently only have 40.
- Inserter activates
- Inserters pull turrets out of an assembler into an active provider, until the active provider has 10 (or 12) turrets in it, bringing the logistics network inventory to 50 or 52 turrets.
- Inserter deactivates.
- 3 logistics bots grab the 10 or 12 turrets out of active provider
- logistics network now reports only 40 turrets again, so inserter reactivates
- inserters deposit another 10 or 12 turrets into active providers, then turn off again
- more logistics bots grab the 10 or 12 new turrets out of active provider, which turns on inserter again
- cycle repeats until the first logistics bots finally deliver the turrets to the storage chests
- logistics network now reports 50 or 52 turrets, permanently deactivating inserters
- all logistics bots enroute finally arrive at storage chests
- storage chests now have 60, 70, 80, or more turrets, depending on bot travel distance, far more than the number I actually wanted.