Hi
So what's going on here? Stuff like iCloud cache the file off somewhere. File shares take a while to respond. The Finder has a timeout somewhere in it that simply isn't right when running on an M1 or M2 based Mac.
What should happen:
I ask for a file
Finder goes to look for it
iCloud or whatever heads off to say "got it"
Finder comes back after that reply and says "here it is"
What does happen:
I ask for a file
Finder goes to look for it (the first time)
iCloud or whatever goes off ...
Finder decides to kill the process ( = Timeout ) and reports "nope, not there"
In some cases the iCloud process. isn't fully killed and the next time you click, it's there.
In other (= most) cases the process is killed fast enough that it's not going to get there
Is that the full story? Of course not. It's about 95% of the story. You can copy / move the files just fine. They *are* in existence. Finder can get at them. It simply is a bug in the "let's open a file" code. It quits too soon.
Does any of that help anybody? Nope, not in any way at all. The *only* thing that will help is an Apple dev guy actually diving into this. The previous comment about opening a case with Apple *is* the only way to stop seeing this "fine stuff" ( I could use a different term ...... ).
Bob