On average, a QlikView setup works the other way: for updating a QVW document in a reliable way, you start by getting fresh data from your data sources by running QVW2. If and when that action is successful, you can trigger your end-user facing dashboard to reload itself from the updated set of QVD files. If the reload of QVW2 wasn't successful (for whatever reason), the Dashboard shouldn't move and keep displaying the old data set.
By using this sequence, you can
guarantee your end-users that something consistent is shown in the dashboard
make sure that and end-user doesn't have to wait for a sequence of reloads to finish, because all of this usually happens behind the scenes (if you're publishing your documents on a QlikView Server)
In a Qlik world, end-users do not often trigger reloads. The server does that, and at specific controlled points in time only.