🧡 Skip to main content🔎 Skip to search

After its completion the App Information Action retains the queried information on the running application or background process in dynamic variables.

The dynamic values can be retrieved by the means of Variable Wizard and used for automatic ad-hoc configuration of the next Actions, for example, the memory usage can be used in conditional branching.

Executable Full path and executable of the app or background process.
App name Friendly name of the application.
Process ID Unique process identifier in Windows.
Memory Amount of memory (in bytes) reserved by the app.
CPU time · s The time (in seconds) the app has spent running is represented by its CPU time in Windows. If the app runs on multiple cores simultaneously, this time reflects the cumulative sum of time spent on each of the cores.
Details Returns key/value pairs of the additional information · Further info
Completion statusRetrieve Action execution status with a possible value—Successful or Failed. Or Empty, if Action has not been executed yet.
AdjustStreamline creation of Task workflows even further—instantly make quick variable adjustments such as in-place replacement (all, first, or last occurrence), trimming (whitespaces, quotes, etc.), or changing capitalization. Optionally, set a different display name.

App details…

The names and values match the Windows Task Manager used schema. Because this list can be expanded in future, it is recommended that the Lookup Text Action (with the Advanced grid option) is used for simple, easy, and consistent value retrieval.

Version 12.4
Process priority Normal
Process priority boost Enabled
Process ID 15356
Process ID (parent) 12516
Logical processor groups CPU0
Logical processors (bound) 0|1|2|3
Logical processors (available) 0|1|2|3|4|5|6|7
Working Set 61915136
Working Set (peak) 65572864
Commit Size 45555712
Commit Size (peak) 49516544
Non-Paged Pool 37560
Non-Paged Pool (peak) 1260936
Paged Pool 324640
Paged Pool (peak) 382360

Automatic list processing…

The App Information variables returned as lists (even multi-level) can be automatically processed in further Actions. Use the For Each Action to parse a given text string (any list variable) and sequentially retrieve its elements one by one · see list processing examples. Or, use the Split Text and Lookup Text Actions to access list elements by their indices.

Need help?

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