Navigation
- Open URL
- Reload / navigation settling
- Wait for page or Smart wait
- Switch/follow target when unambiguous
Automation Studio reference
Use this as the quick reference after you know the basics. It describes the major action categories and reliability rules without making you work through the full course.
Reference
Use this page as the fast lookup reference; use the full Automation Studio course when you need the learning path.
Execution semantics
The current Automation Studio is designed to handle common browser instability instead of forcing users to tune every low-level wait.
Prefer a condition or Smart wait over arbitrary fixed delays when the next step depends on page state.
Redirect chains and a single clear target replacement can settle before the next step.
A download can be treated as complete only when the file operation actually finishes.
Rerendered inputs can be reattached when the replacement is unambiguous.
Recovery is allowed when the target context has one clear match; ambiguous cases should not be guessed.
Important actions should check the expected effect instead of treating input delivery alone as success.
Core model
Keep the three objects separate so a workflow stays reusable.
The ordered browser logic and Actions.
Targets, windows, concurrency, timeouts and execution policy.
Binds one Workflow and one Automation for manual or scheduled execution.