What build were you using? When I try the exact same thing here using the latest beta I'm getting the expected error: File not found. Essentially you described a process of queueing non-existing files, ie. files that were present at the time of queue-creation, then either were deleted or moved. Quite the common scenario on a busy server.
What probably happened is that most servers are able to cache the new link of moved files so that a queue thats underway while files were being moved won't stop/break until - at the earliest, when the present file is completed, or at the latest, when the current diirectory is completed. The server you were using obviously attempts the same but fumbles and lets you get the files, which end up as 0-byte because its cache is bad.
|