Hi @jumbojake ,
Thanks for your post and apologies for the inconvenience. I was glad to read that you found a work-around (spot-on).
Based on your description, I believe it aligns with an issue we were having which is marked as solved around 2h ago by our development team.
Could you kindly:
1) Check if the issue remains?
2) If yes, raise a case with support so we can investigate further?
Thank you have a great day ahead of you.