We just got v1.4 deployed and the issue remains just as Myriam described it @lin_d_hop @CynthiaReynolds