I'm guessing your screenshot is from your iPad and that you are using default Safari browser?
If Safari is up-to-date - then it might be an issue with how FamilySearch site interacts with that browser. The first step generally is to make sure you have updated your browser to the latest available.
My best guess is- if you refreshed the page the [Unknown Name] would resolve? It appears to be a timing issue - the page is not resolving the name though it has an ID (though interestingly it appears to be the exact ID you are performing a search for - yes that is a bit bizarre.).
“does not exist “ or “restricted”- are different issues I believe. If you give an example/screenshot of those - someone can respond better.
My impression or understanding is that FamilySearch pages -- like all complex webpages nowadays -- are built up in layers: there's a base layer that the link fetches, then there are all the bits and pieces that replace parts of that as queries are made to the various databases. If any of those queries takes too long, or returns an error code, then the underlying base state "shows through" -- which is usually a placeholder or error message. Hence "[Unknown Name]" when the query with the PID didn't go through yet and your browser got impatient.
The first thing to try is to give your browser a light thwack on the head, by using the "refresh" or "reload" button: "try that again, please".
Sometimes, that doesn't help, because the browser has "helpfully" saved the faultily-loaded page and is fetching that instead of actually making a new request to FS's server. (Refresh/reload should technically override that, but our devices all Know Better Than Us, you know.) Clearing your FS-related cache and cookies should remove that problem.
I'm not sure why or how updating the browser helps, but it probably resets a few cookies, and maybe reminds the browser to wait a few seconds longer for queries to go through.
I'd like to briefly expand on the clearing cache comment.
In my experience, clearing data cache is usually enough. You can typically leave your cookies (and your session login) untouched.
If you want to clear cookies: Many browsers let you clear stuff per site. This is great for clearing cookies. You'll want to clear for sites with familysearch in the name. It won't mess with logins for other sites
For data cache, you'll want to clear everything for everywhere. It's all upside and no downside (typically, because computers).
For the screenshot in the OP, I've seen that in desktop browsers (Firefox, Windows).
IIRC, 1) I've never seen it in mobile browsers and 2) a page refresh didn't make a difference.
Item 1) supports the theory that clearing cache will resolve it. I haven't put that to a test, however.
When I access the record, no errors are appearing. It may be a temporary glitch somewhere between your computer and FamilySearch.
I suggest you try the following:
Hopefully one of these will resolve your issue.