Hi @rozgwi. Thanks for flagging this up. As this is marked as solved it’s unlikely it’s tracked internally any more, but I’m afraid I no longer have access to the internal tracker to check.
You’ve also flagged up this other similar bug. Does that override your comment here? Are they the same or different issues for you?