For example when I place assembler and inserter which are still ghosts, and i set a recipe on the ghost-assembler, for example the heating tower:
Shift right click on the ghost-assembler
shift left click on the ghost-inserter (which goes from the ghost assembler to a ghost passive provider)

I would exact the limit to be set on the logi network, and that the filter would become whitelisted heating tower. Whats happens is that i get indeed the logi limit, but i get the ingredients set in the ghost-inserter whitelist filters

Thanks for the detailed repro steps - that helped pinpoint it.

What was happening is exactly as you described: with ghost entities, vanilla paste can leave the inserter filters on assembler ingredients, while APS correctly sets the logistic-network limit from the ghost recipe. So you ended up with mixed behavior (correct limit, wrong whitelist).

I’ve added a fix so ghost assembler recipes are read correctly in this flow, and when pasting to an inserter that picks up from a ghost assembler, APS now forces the inserter whitelist to the assembler product (e.g. heating-tower) instead of leaving ingredient filters.

If you can, please retest on the latest build and let me know if your exact setup (ghost assembler -> ghost inserter -> ghost passive provider) now gives:

logistic condition: product with expected limit
inserter filters: whitelisted product only
If you want, I can also give you a shorter “mod portal style” version of this reply.

Nice, thank you!

How now i find, when you now click a normal inserter again, to increase the logi limit, the whitelist filers get changed to ingredients again.

Not fixed when shift right clicking an already built assembler, then shift left click on a ghost requester chest.