As written above, 7.7.3 will resolve this when its released.
It wasnt caught on test servers because we were using databases with fewer than 500 accounts.
Once the issue was found (one week after 7.7.2 was released, which was about 10 days ago on July 2nd), a solution was written and a plan for deployment was made. You'll see the fix in 7.7.3 release, which should happen soon.
I have not upgraded yet from 7.7.1 > 7.7.2
Now that I read above about the 7.7.3 fix I'm thinking of waiting since we have 10000+ members
So should I wait for 7.7.3 or do the 7.7.2 upgrade anyway?
