🧡 Skip to main content🔍 Skip to search

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.

WaitDetails
ProcessSelect a process or app to wait for:
  • Simple · choose a name from the list.
  • Dynamic · provide a name of executable (with an optional path). Utilize the Variable Wizard to incorporate input from variables.
  • Process ID · use a process identifier (usually using the Variable Wizard PID value that is returned by other Actions or Triggers).
App infoShows the current status of a process or application, for example:
  • The application "Settings" is currently running.
  • The process "Lighting" recently was closed.

The tooltip displays extended process information in real-time.
Condition Choose one of the two conditions to wait for:
  • is running · the application is currently active, operational, and processing data as intended.
  • is not running · the application is inactive (closed or terminated).
Start menuStart menu buttonChoose an App using the virtual Windows Start menu. All the necessary app parameters will be prefiled automatically.
BrowseBrowse buttonUse Browse to select a particular file or folder on local disk, network share on LAN (local area network), etc.
Variable WizardVariable Wizard buttonUse dynamic data input—substitute a parameter from a file, web, connected Trigger, other Actions, date and time presets, etc.

Interconnect

  • Wait for App integration and auditing—Variables (dynamic data) and Events (recorded activity). 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.

Delay options…

Automation Workshop includes options to pause a workflow and conditionally wait for different resource types. These waiting Actions operate similarly—they pause the workflow until a particular resource reaches a desired state, such as when a file appears or disappears.

More app options…

Automation Workshop offers a comprehensive set of Actions to monitor, control, and modify Windows application states and properties. These tools allow you to automatically start processes, manage running applications, and terminate them as needed.

Notes

  • 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.

How seamless automation works? A 90-second demo.

Help at your fingertips…

If you have any questions, please do not hesitate to contact our support team.