mshepard

Hello, I can confirm that the issue has gone away with 3.4. Thank you!

@matthew

I agree. I'm not getting the error any more with 2026.3.4.0.