Thank you!
I saw a similar post here back and someone else reported the same or a similar issue.
According to the discussion point, it looks like the Engineering Team was aware of this issue as of August 23rd and planned on fixing it in a release.
Is there any idea of when that timeline is? I’m trying to work with our marketing team on this and if it’s something that’s been known since August, I just want to get an idea of how close that release may be, otherwise I’ll have to work on a different solution with them.