I upgraded from 2.4.2.126
→ 2.4.2.129
and can confirm that it has resolved the issue as noted in the 2.4.2.128 release notes. Thanks again for the quick response!
3 Likes
I upgraded from 2.4.2.126
→ 2.4.2.129
and can confirm that it has resolved the issue as noted in the 2.4.2.128 release notes. Thanks again for the quick response!