Hi all—what’s the best way to keep a single Calculator instance when a workflow uses Parallel or Retry logic? I’m seeing multiple calculator.exe processes spawn, and selectors bind to the wrong window. Environment: Studio 2023.x (Modern), Windows 11, Calculator (Standard). Current approach: Use Application/Browser to open Calculator, then run all actions inside that scope. Still, during retries or parallel branches, another instance sometimes launches. I’m weighing three patterns:
Guard + Attach: kill any existing process at start, open once, attach in every branch.
PID pinning: capture the calculator PID and inject it into the Attach Window selector.
Singleton launch: if process exists, attach; else start, then attach.
Questions: Which pattern is most reliable unattended? Any selector fragments (UIA vs Default), Retry Scope placement, or sample XAML to avoid duplicate launches? Bonus: tips for resetting state (AC/C) without spawning a new process, and ensuring “Get Text” reads from the correct display.
Hi,
Can you try as the following?
First, Open Calculator with SingleWindow mode and set UiElement variable at Output element property in UseApplication/Browser activity.
If it’s necessary to handle same calculator later, set the above UiElement variable at Input element property in another UseApplication/Browser activity..
Regards,
Are you seeing this pattern even if you select open if not already open property option as well?
One way would be open calculator before paralle and thwn in parallel use open with never so that it would always try to attach
Cheers