Hi @Matt_N Thank you for reaching out! I believe our team fixed this bug Can you confirm if you're still seeing the issue?