As previously posted here, this is happening once again.
Hello @MSStateDawg,
Thank you for reporting that this is happening again.
This issue has already been reported and escalated internally under CTP-16412, and our teams are actively working to correct the behavior. At this time, we do not have an ETA for resolution.
We appreciate you continuing to bring this to our attention and your patience while it’s being addressed. Please feel free to share any additional details if you notice changes in the behavior.
Thank you!
I see the latest update released just now contains a fix. Thanks.
@MSStateDawg Thanks for the update! Glad to hear that.