It would seem you’ve confirmed that it’s the exact same issue reported in February (and never resolved?) …