It’s possible this was fixed in Build 128 @Abe_Abrahamian, but let us know if you’re seeing otherwise.
Thanks!