You should no longer see this issue after reloading your documents. We have also identified and fixed the testing gap that let this regression slip through. If you would like to know more about what happened please read on.
The connection between the formula engine and action engine is a bit complicated. The RunActions formula creates a transition boundary between the two engines, so we have to package up all data in the formula’s execution context and pass it to the action engine so it can execute the nested formulas with all of the outer information.
A recent document upgrade changed how we stored RunAction formulas so that we could more quickly push out optimization changes for those formulas. It turns out that the previous formula storage was rewritten in such a way that didn’t trigger some of our normal formula validation rules, most notably valid Row.Column dereferences. When this change rolled out we exposed the fact that not all context captured by the RunActions boundary was being passed to our compiler even though it was already being passed to our formula execution, which is why existing actions started failing when trying to compile and execute their nested formulas.
Sorry about the regression. Please let me know if you are still experiencing any issues.