This sounds like a known bug (345021) found in 2020R2.5, which seems to be reappearing. Although the workaround that has been found helpful so far is to rerun it. But it looks like that is also not working for you. (Can you please try doing that again?).
If I remember correctly, the same file had no such issue solving earlier, so I do not think this is a problem with your setup. I will test it on my end and see if even I face the same issue, if yes, I will get in touch with the developers and see what can be done.