When a c-combinator attempts to set a recipe that hasn't been researched or otherwise has no valid recipes, it blocks valid recipes from being selected.
context: I'm making a machine that walks through a long self-dependent recipe, ending in one I haven't yet researched but want. All products are being used.
Example: In Space Exploration, inserter crafting takes the previous tier of inserter. Burner->Standard->Fast->Stack. In this example, stack hasn't been researched. The first time the crafting combinator attempts to select it, it will fail and never set anything again, despite demand for the other types resurging due to being used.
Expected behavior:
When presented with multiple recipe signals, including a bad recipe signal, it should ignore the bad signal
Actual behavior
The c-combinator enters a fail state it won't recover from unless the bad signal is removed. (untested if it recovers on researching the recipe, likely not.)