Hey @BartCoppens and @bryant_baird_dev thank you both for your reports here as well. Just wanted to confirm that I was able to speak with the product team on this and we’re looking into this as a potential issue on our end. I don’t have a specific turnaround time for a fix or what the fix would look like at the moment, but I’ll keep my eye on this for you all here and update you as soon as I have more info/next steps to share.
For your other thread @bryant_baird_dev , it does look like the same issue. I can close that out on my end for you so that we don’t have any duplication, thanks for flagging that!
I’ll update you all as soon as I hear from the folks I’m working with internally on my end here, thanks again for your patience on this 