API

If a supported API can make the whole change, call the API and you’re done. If one developer owns a script and watches it run, keep the script. Record a workflow in OpenAdapt for the step that’s left over, the one that only happens on screen. That’s worth doing when other people depend on the step and you need proof that each save landed in the record. How the options compare Option Who owns it What checks the save After a timeout Switch when Supported API Your developers call it, and the vendor keeps it stable The response, plus your own read of the record Read the record before you send again It can’t reach a step. Move only that step. Playwright A developer The script’s assertions Before the click, it fails with nothing clicked. After the click, your code has to check the record. Other people depend on it, or the task leaves the browser Selenium A developer or test team The test’s assertions, plus any record check you add The browser error can’t say whether the save landed Other people depend on it and nothing reads the record, or the task leaves the browser AutoHotkey The person who wrote the macro That person, watching it run That person sees it and fixes it by hand Coworkers copy it, it runs unattended, or a bad save is costly OpenAdapt workflow A named owner, who reviews each change A separate read of the saved record, set up for each workflow It stops and asks a person to check the record. It doesn’t retry on its own. A supported API starts covering the step Tool behavior in this post comes from each project’s documentation, checked on 2026-10-09. ...