- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2019 07:42 AM
i am getting the below error when discovering a device. how do i increase the timeout and what should be the ideal max. timeout?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2019 09:43 AM
To change it for all probes, mid parameter mid.windows.probe_timeout should do the trick.
For just one probe, use probe parameter wmi_timeout. (Yes, "wmi," even for powershell.)
- Tim.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2019 07:52 AM
Hi,
Try setting mid.powershell_api.idle_session_timeout to the desired timeout value.
Might require some trial and error as if you will set it too high you might trigger other global session timeouts.
Hope this helps.
If it does, please mark as helpful and share your results.
Asi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2019 09:43 AM
To change it for all probes, mid parameter mid.windows.probe_timeout should do the trick.
For just one probe, use probe parameter wmi_timeout. (Yes, "wmi," even for powershell.)
- Tim.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2021 03:35 AM
As i know at present PowerShell timeout properties do not apply to Flow Designer PowerShell step.
It will be fixed in San Diego.