I play the ATM10 modpack (RS version Neoforge 2.0.0 beta2). I made a simple autocraft, for example 10 Gold upgrade for Functional Storage. As a result, the autocraft just freezes and does nothing. Time goes by, the craft hangs in the crafting tasks, but no activity occurs. Of course, there are related machines and resources for crafting. As if something happens with the calculation (plan) of the craft and everything freezes. It can hang like this for 10 and 20 minutes and there will be no result. It helps to make fewer items, but for some crafts this is only one item, which makes the autocraft useless

I found relogging the world helps, I had this issue with mekinism autocrafting, it would craft the alloy alone just fine, but when I would request a speed upgrade it would just not do anything. But relogging somehow fixed it

I find this sometimes happens when requesting something while another crafting operation is already running that requires some of the same materials.
The second newer autocrafting request sometimes "steals" resources from the previous ones, which hangs them as they are waiting for machine output that has already been consumed by another task.

@LoaderB0T Yes, i know, but not in my case

Not sure what to do with this issue. If you were me, how would you reproduce and fix it? Are there reliable steps I can follow?

@raoulvdberge Found why. If you store resources in the Compacting Drawer (Functional Storage mod) - in particular, if you put a gold bar there (and get automatic conversion piece-ingot-block). As a result, if the recipe contains a gold block and a gold bar and some of this is not available (but there is an autocraft recipe), then it hangs on the crafting of the gold block because autoconversion produces the block automatically. Apparently RS does not understand this and as a result the task hangs. At the same time, if you prepare the required number of gold blocks and bars in advance - it works fine.

I tried to explain as best I could :)

Ah, that makes sense. The calculation makes a wrong assumption because of the compacting drawer. I'm trying to understand if this was an issue in earlier versions of RS.

The same issue exists in Refined Storage 1. Since autocrafting relies on simulations before starting the task, we cannot anticipate for items just disappearing if other items are gone.

However, it should be more clear from the crafting monitor that the task is stuck extracting initial resources.

The root cause is difficult to fix, but I have added some measures that make it more clear to the user.

1: Show crafting task state

2: Show resources which still need to be extracted from the storage