Export Bus with Crafting Card skips activation cycles after task cancellation or CPU disconnection

[LemonedQ]

Describe the bug

When an ME Export Bus (equipped with a Crafting Card) is performing a crafting task, if the task is manually cancelled or the CPU is disconnected, the Export Bus fails to initiate a new crafting request on its next activation pulse. It appears to skip cycles or enter a redundant "cleanup" state before it can request again.

Specifically:

• Single Item: After cancellation, the bus stays idle for one activation and only initiates a new request on the second activation pulse.
• Round Robin Mode ($n$ items): If $n$ items are filtered and their active tasks are cancelled, the Export Bus will skip the next $n$ activations (one for each filter slot) before it starts issuing requests again. This creates a loop where it "works for $n$ activations and skips for $n$ activations."
• Default Mode: Even with multiple items filtered, if the first item's task is cancelled, the bus remains stuck attempting the first item only every other activation, failing to utilize the "skipped" cycle to check other items.

How to reproduce the bug

1. Set up an ME Network with an autocrafting pattern and a Crafting CPU.

2. Attach an ME Export Bus to a container and filter it for an item with a pattern.

3. Insert a Crafting Card (maybe an Redstone Card as well to manually active the bus with redstone pulses).

4. Configure the bus to "Always Craft".

5. Once the Crafting CPU starts the job, manually cancel the job or disconnect the CPU.

6. Observe the Export Bus's behavior. You will notice a distinct gap where the bus is active but fails to send a new crafting request to the network for one or more cycles.

Expected behavior

When a crafting task is cancelled or broken, the Export Bus should detect the invalid state and initiate a new crafting request on the very next activation cycle. There should be no "skipped" cycles or idle pulses regardless of the number of filter slots or the scheduling mode.

Additional details

No response

Which minecraft version are you using?

1.21

On which mod loaders does it happen?

NeoForge

Crash log

https://gist.github.com/LemonedQ/c6c057a1cf42b6e006e635c99d4e50c8