I believe I made some progress for anyone reading this.
In order to debug this problem further - I had stripped down all the formulas in workbook on the most computationally complex worksheets.
FYI: An easy way to do this is just to search and replace all "=" with an unusual string, I use "meow". I then add back formulas one by one until the error is triggered.
The problem appears to have triggered at Lambda functions. I use the ByRow function a number of times.
=IF($E25#="UN",0,IF(GO$21="OFF",1,BYROW(EW25#:EZ25#,LAMBDA(x,IF(ISERROR(PRODUCT(x)),0,PRODUCT(x))))))
E25# contains various text string codes. If the value is "UN" it just returns a 0
EW25# to EZ25# are small numbers between (0 and 1)
The function above, that worked great for years, seems now be triggering the insufficient resources state.
----------------------------------------- Yes that seems to be the trigger
I tested it by creating four spillable sequences as shown below (Columns FA, FB, FC, and FD) They are 650 rows long and the formula in FE triggers the issues.
****** This is clearly a Microsoft update error, a formula that worked for three years shouldn't be triggering this. Especially with something as basic as multipying integers in for only 650 rows.
![](https://learn-attachment.microsoft.com/api/attachments/cf4713b8-5035-4dd0-81eb-902a17cd2e38?platform=QnA