Alexandra Beisl 

I guess one reason, assuming you are doing everything correctly, could be working with your project on OneDrive or some other network drive.  If you do use a drive like this try working on your local drive in a folder that is not synchronised with whatever network drive you are using.

I am working on my local drive. And I have tried browsing for the actual file, but on finding it and trying to add it back in within the project, as suggested by some, the error still persists. It is as if the bilingual review process persistently "spoils" that file within the package. I had to start new with the TM from the first run as the client insists on a target language file. But the actual match values are gone and they won't be pleased about that as they now cannot filter for new translations, as everything looks like a 100% match. I have no idea, why this problem should crop up now. BTW, I am running the latest version of Studio, so the software is up to date after my latest update last week.

I am working on my local drive. And I have tried browsing for the actual file, but on finding it and trying to add it back in within the project, as suggested by some, the error still persists. It is as if the bilingual review process persistently "spoils" that file within the package. I had to start new with the TM from the first run as the client insists on a target language file. But the actual match values are gone and they won't be pleased about that as they now cannot filter for new translations, as everything looks like a 100% match. I have no idea, why this problem should crop up now. BTW, I am running the latest version of Studio, so the software is up to date after my latest update last week.

Alexandra Beisl 

Go to your Project settings, open File types, go to SDLXLIFF, click General and increase the size of the embedded file. Most probably your source file is bigger than 20 MB and this will not be stored within the sdlxliff.

Thanks Jerzy. I checked the size of the source file and it is way smaller than that. Also, that size had already been increased beyond 20 MB in the past. So I don't think that is the problem.