@DoninGA
It's March 1, 2025. The bug is not fixed yet. @DoninGA said it's a known issue, but there is no tracking info. Could you re-escalate the issue as "not fixed" so that it is tracked properly? Thanks.
