Manufacturing bug

[mr blade12]

I have been experiencing a bug when it comes to the phone's Manufacturing the assemblers likes to go into the off status making it impossible to get finished product the only way I can get them to turn back on is if I buy a new one but within a couple seconds it would just shut off anyway

[AbysmalCraig]

I'm Having this issue, my assemblers efficency goes to 0 with no explanation

[egorpuzyrev]

Same here. Effectiveness turns to zero after few minutes of game running. Component Assembler status shows something is queued, but nothing is being produced. If i got it right, Component Recycler, which actual purpose stays unclear for me, should prevent producing pipeline of getting stuck, but it just recycles _everything_ that goes into it. Manufacturing tutorial is pretty poor and does not cover any of related nuances, so i can not really understand, is it a sort of bug or is it just undiscovered/unexplained game mechanics.

[LatN's Strategy]

Go to the MFG room, there is a Data Overlay (O), above the build menu, looks like stacked papers icon. click on it and click on MFG. That should show if there is any issue in the MFG process chain. If not here is a video that shows layout and how to check it.
https://youtu.be/oPKzzJwsSyo

[elphaba.thorpp]

Same issue here. Checked all my lines, no issues, nothing disconnected, nothing going in the wrong direction. The line just won't fully complete the contract/deal it's assigned. It will stop production with maybe 5-10% left, and the assemblers have an efficiency of 0% and the whole line turns off. Cannot figure it out, I've rebuilt so many times. Tried recyclers after each assembler (which just ate everything) and then tried a single recycler at the end of the whole process (which i think is how it's meant to work). Still doesn't fix the issue.

The only work around I've found is to duplicate a new line when the original gets stuck, delete the original and then let the new line run. Occasionally it will finish the contract before stopping, otherwise if it does stop I have to repeat the duplicate process again.

Is there something in the mechanics I'm missing, or is this a bug?