Thanks for the added note. It appears that the team has identified the issue and has a fix in testing. It is unlikely to drop until the quarterly update, though please feel free to make a case that lets us know this is significant enough to warrant prioritizing over other issues. Otherwise, keep an eye out for the fix in a future update!