EXECUTE Failed to load .qvw failsafe

[fbottinelli96]

Hey community!
Im having a problem with an automation process I created, which executes a series of QVW within a FOR. Mostly, this process works perfectly, but lately I've been having some issues with the disk these QVW are stored in. I know thats the problem, but I like to work on failsafe over failsafe for this kind of problems. 

Anyway, the issue is that this disk is being unstable, and sometimes when I execute the reload, Qlikview opens a new tab and a Windows warning pops up saying "(FileName QVW) Failed to load". This type of error shuts the entire chain of automation, since the EXECUTE command is kept waiting for an answer from this QVW, which it doesnt get.
SO... Is there any way I can let the main automation QVW know that this QVW failed to load? So it can move on?
I know this doesnt solve the root of my problem, but I need to fix this asap, and the disk issue if a big fix right now (I'll get to fix that in the future)

The closest I got to solving this problem was to execute a parallel process before this reload that kills the task within 3 hours (these QVW usually take 2 hours to run at worst), but I cant seem to execute a parallel process without the Execute waiting for it to end as well.

Thanks to everyone that takes the time to read and help me with this issue

[Brett_Bleess]

Given this is really OS related, not sure there is any means to do things from our side unfortunately.  The only thing that came to mind was seeing if you can check on any QV.exe processes and if any are at 0 or some small CPU amount for x minutes, then kill the process...  I am no PowerShell guru, but I would think there are likely APIs to do this, but I do not know them off the top of my head.  Whenever folks try to run things via commandline, we generally recommend doing cmd.exe /c which tells things to shutdown once they finish, but I do not know if it would take the dialog as a means to shutdown or not in this case.  I think the only way is to check the QV.exe CPU usage, as if it is hung on a dialog, CPU should be almost 0 etc. and use that as your trigger, as it should not be idle if things are working properly.  Best idea I have. 

I checked the Script errors, but the issue is you are not even able to get the file opened, so that is not going to do any good, and that is why I said this is really outside our control given it is OS level, not Qlik.  

Regards,
Brett