>>105588017
>Wouldn't running teacache later (at 10% of the steps) fix the issue then?
Assuming it's teacache causing the issue, possibly.