I cannot say the reason why you are using the same QVW in chained tasks, only the developer who created that can answer it.
In my case, I would never go that way, and use several different QVWs in each step, unless there is a very good reason not to.
Are those tasks reload tasks, distribution only, reload and distribute?
Is the document never available to any user, or it is available to some users but not to others at the same time?
Basically, a document will be available in the AccessPoint when:
1.- You are using an authenticated account (NTLM, Headers, others)
2.- You are authorized to see the document (in QlikView QMC when using DMS and in the Operating System when using NTFS)
3.- If the app is using section access, you are a member of such table with access to some data after the data reduction happens
Even if the file is being reloaded, the QVW should always appear in the AccessPoint except, maybe, for very short periods of time while the QVW is being locked and written and somehow the Web Server cannot reach that file, which can happen especially if the QVW is large, several GB in disk, and writing the file can take a few minutes.
2.-