@o1i let me know if you experience any issues using the updated stack code

I have a workaround now 😉 but I will revert it and test.