Powershell default timeout value
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-23-2015 07:25 AM
Hi
We are working with making a workflow with different power shell nodes and Run Commands nodes in SNOW.
I want to increase the default time-out values for the Run Powershel node so that it wont exit the node till it receives the output from the script.
The script takes a pretty long time to execute since it has to wait until the backup is completed successfully say(30 mins).
So where can i change the default execution value so that it does not end before it receives the output from the script.
Thanks in advance
Regards
Darpana

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-28-2017 10:12 AM
Looks like this question was asked back in 2015, and since the Run PowerShell activity has been deprecated in favor of custom powershell activities (and even those will be depreciated in favor of the new Integration Hub come Kingston).
However the question is still relevant and to extend the default powershell timeout, you need to change a MID server parameter called "mid.windows.probe_timeout". It stores a number value in terms of seconds. So if you want the timeout to be one hour, enter '3600' for the value. You can read up more about them here: MID Server parameters
Regards,
Tyler
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-28-2017 10:49 AM
We are running Istanbul. I have Administrative privileges in DEV and TEST. In DEV, I go to MID Server Properties and all I see is this:
Do I need to ask someone who has Administrative Privileges in PROD to actually be able to access the "mid.windows.probe_timeout" parameter?
Thanks,
Mark

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-28-2017 11:13 AM
Hey Mark!
My bad, I linked the wrong MID server properties documentation, it's actually a MID Server Parameter, I'll go and update my prior response.
I'm not sure if you need admin, but I believe you do, so you may need to ask yes.
If you go to Orchestration > MID Servers > Select your MID server > Scroll down to the "Configuration Parameters" related list, and then add that parameter I mentioned.
It'll look like this: