We've been on 23.1 Build 480 since it was released and we still have the issue.
We also did a clean install of 23.0 and updated to 23.1 and it did not correct it, so it appears to be on the Ancestry side.
We also did a clean install of 23.0 and updated to 23.1 and it did not correct it, so it appears to be on the Ancestry side.