Wait for Ping
The Wait for Ping action sends a ping to the computer with name or IP address that you specify and then waits for the ping to succeed or fail.
Note: The Actions Quick Reference provides a complete list of actions that you can print for easy reference.
Creating a Wait for Ping action
-
On the Actions list, click Computer and select Wait for Ping.
-
Enter the Host name. This value can be the host computer name (MyComputerName), the fully qualified name (MyComputerName.Domain.com), or an IP address (255.255.255.0). Optionally, click the Magic Wand to use the Expression Builder.
-
In the Timeout field, determine how long the action should wait for a single ping to complete and enter the time to wait. Optionally, click the Magic Wand to use the Expression Builder.
Note: This value is different than the Wait up to value, which is the amount of time the action will wait for the desired response.
-
Select how you want to Wait for the ping: Ping to succeed or Ping to fail
-
If needed, adjust the Wait up to timing settings and enter the amount of time the action will wait for the desired response.
- Do not wait
- Wait up to
- Wait forever
-
If needed, adjust the Run error task settings to fine tune how the action runs.
- Run error task: A botflow containing an error task automatically runs the error task in the event of an error. If the botflow does not contain an error task, the botflow stops in the event of an error.
- Stop on error: The botflow stops in the event of an error.
- Ignore errors: The action is skipped in the event of an error and the botflow attempts to execute the next action.
-
(Optional) Add a Note to document special instructions or functionality.
-
Toggle the run switch to Run and click OK to execute and save the action.
Note: The run switch is set to Run by default. To create or modify this action without executing it, click the slider to change the option to Don't Run. For more information, go to Action Builder.
If the action timeout (Wait for value) is set up to wait for 100 milliseconds for success, but the action desired response timeout (Wait up to value) is 300 milliseconds, then the action will continue to wait for success. In this example, when the action runs, Nintex Bot will send a ping that will time out after 100 milliseconds and then return a failed or success message. Since the action only waited for success for 100 milliseconds before timing out, Nintex Bot will send a second ping for success that will time out after 100 milliseconds again and then return a failed or success message. Again, since the action only waited for 100 milliseconds for success before timing out, Nintex Bot will send a third ping for success that will time out after 100 milliseconds again and then return a final failed or success message because the action desired response timeout has now been met.