The Wait for App Actions pauses a workflow until the specified application or background process changes its runtime status. You can choose to wait for an app to be running or not running before continuing with next Actions.
|Select a process or app to wait for:
|Shows the current status of a process or application, for example:
The tooltip displays extended process information in real-time.
|Choose one of the two conditions to wait for:
|Choose an App using the virtual Windows Start menu. All the necessary app parameters will be prefiled automatically.
|Use Browse to select a particular file or folder on local disk, network share on LAN (local area network), etc.
|Use dynamic data input—substitute a parameter from a file, web, connected Trigger, other Actions, date and time presets, etc.
- Dynamic variables & Events of the Wait for App. Access the executable name and its process ID. Additionally, log information events indicating that the Action is waiting for an application or a timeout has occurred. Log failure events to show errors encountered while waiting for an application or when a timeout concludes with a user-specified error condition.
- If an application name is provided as the input value and multiple instances of the same application are running, the Wait for App Action waits for any instance of the app that satisfies the waiting condition.
- If multiple instances of the same app are running, and the workflow is set up to wait for the app is not running, the Wait for App Action pauses the workflow until all the app instances have exited.
- If a process identifier (PID) is specified as the input, the Action waits only for the specified instance.
Help at your fingertips…
If you have any questions, please do not hesitate to contact our support team.