Intel Mac "tell application finder" problem?

Question

Ok, on my Macbook pro....
I have some file exists type commands, a duplicate, etc. in an Applescript. It is behaving as if the Applescript spawns a second finder.
Several issues. First, if I run the finder, and look in a network folder, I see no files. I then run the script through the script editor run command. The script then says the file exists! It does not. To be more precise, the first invocation it doesn't exist, the script triggers a process on another machine which creates the file, the script then process and deletes it. So, it does not exist again. Run the script again, and, it says the fie is already there (this is a sfaety check), it is not there when you look in the finder, and, using terminal window.
By adding update every file with necessity over and over in the script, it does behave properly.
Does Applescript not use the same finder already running? I find it odd it says a file exists yet using the finder it does not. This can carry forward minutes into the future and occurs over and over.
What am I missing here?

Answer 1

It's hard to tell from your description, but it's known that the Finder often uses a cached view of network volumes, meaning that there's a delay between something being created on the server and it appearing on your desktop (and conversely a file being deleted off the server and disappearing from your desktop). The amount of delay varies on some basis that I don't understand, but the simplest fix is to tell the Finder to update the file or directory you're dealing with right before you reference any shared volume. This ensures it has a current view of the server volume.