I am running a .vbs script after the end of the workflow using Events, it runs perfectly but recently i got a strange timeout error for C:\windows\system32\wscript.exe. If anybody could suggest what could be the issue here?
Regards,
Paras
I encounter the similar issue when I try to execute a vbscript to trigger excel macro. I am curious why such error will come up.
From my understanding, once the script is triggered, the macro and relevant process are already out of the alteryx control. Why alteryx will still count the timeout time?
I would like to understand more about the event works.
The vbs is primarily triggering the a xlsm file and macros in it. Nothing that should take up more than 30s. It does not happen every time I run it.
Higher value to timeout can help probably..!!
Hi @Paras_G,
Does your .vbs do any "long" -more than 30 seconds- task? What if you set the timeout (In Edit Event window) to a higher value?
Kind regards,
Paul Noirel
Customer Support Engineer
