This happens when the crafting pipe or module isn't the entity to pull the item out of the machine, such as if there's also an extractor module in the chassis or if the machine itself pushes the item into the pipe (such as a GTCE blast furnace). This results in the crafting request remaining in the queue indefinitely.

What should happen is that the crafting pipe or module should notice when a requested item enters the pipe from the machine (rather than another pipe) instead of needing to be the one to pull it out.

I believe this is the intended behaviour, the solution is to not have an extractor module in the same chassis pipe as a crafting module.

Well, the machine is behaving incorrectly if you can't disable autopush. Why is that Logistic Pipes fault?

Afaik there is a plan to improve this situation but I don't really know any kind of details

And what's the solution for machines that push into the pipe?

Attach the crafting pipe to a buffer chest, have the machine pull from, and push to the buffer chest.

If that's really the intended behavior, that seems overly clunky.

There always was this problem with the BC assembly table and it is very easy to workaround, but PRs are welcome.

Duplicate of #255