Hi @Jonnie, sorry, we accidentally ended up rolling back this fix while applying some newer updates, causing this bug to resurface. We’ve re-applied this fix to the UI deployer (more permanently this time) so that should be working properly again, sorry for the inconvenience.