Yes, I can't reproduce the same TypeError message, but I still have the same issue. I checked with our team internally, and they think it is a bug introduced in one of the latest updates. Any other information that I can provide you with to help fix this issue? - thanks