Conditions, loops and action options

Conditions and While

If chooses then/else using a Boolean or supported element-exists/element-not-exists predicate. Presence samples once; use Wait for synchronization. A query failure is not false absence, and presence does not implicitly mean visible.

While repeats its body while its supported condition holds. Do While runs the body before the following condition check. Browser also supports explicit custom JavaScript predicates with a Boolean result; HTML/native targets do not acquire page-code conditions.

Iteration caps

A maximum iteration count can be a positive whole number or a supported literal/variable numeric binding. A numeric control may consume decimal-digit text such as "10"; signed, fractional, blank and mixed text is not a valid integer limit. General fields keep their own stricter type rules.

Zero and negative native caps are invalid, not unlimited. Omitting a cap preserves the source’s default. An ordinary invocation resolves the cap when entering; changing its variable later in that body does not retroactively change the active ordinary loop’s cap.

Repeat On sources

Source	Behavior
Array	Preserve each item’s type, including false, zero, empty text and null.
Elements	Select page rows with target-appropriate locators and inherited child context.
File	Read a supported retained CSV, JSON, JSONL or XLSX input. Legacy XLS is not supported.
Saved records	Traverse current authorized records using the selected query. This is not a fixed-time snapshot.

Without a cap, array/file/record sources use their available traversal. DOM repetition defaults to one iteration; select a larger explicit maximum for multiple rows. DOM rows supply selection/index, not a JSON item value.

Toolbox and ordinary Runs

With Toolbox Debug on, each reached outer While/Repeat On advances once per Play. Nested loops complete. Exhausted loops require an explicit restart. A separate child Play needs an actually retained parent context.

With Debug off, the submitted tree traverses fully. Ordinary Sessions always traverse fully, independently of the browser-local Debug switch. See Toolbox before diagnosing a one-row interactive test as a failed loop.

Success-only children

Ordinary actions may have a body of child actions. These run after their parent’s own success, then execution continues with the parent’s next sibling. The parent’s locator does not implicitly become a new row scope.

A continued parent error skips its children. Each child has its own error policy; an unhandled descendant failure still propagates. If/While/Repeat/Container keep their own branch/body semantics and do not run the same body twice.

Shared options and Exit

Option	Meaning
Disabled	Skip the action and its descendants, preserving editable source.
Custom name	Change its displayed label without changing action type.
Exit on error	Omitted/true propagates its error; false can continue after that action’s recoverable own error.
Timeout	Initial locator-appearance wait, not a complete-action deadline.

Continuing does not replay the action or convert Stop into success. A successful Exit ends remaining execution; a failed Exit errors. Its optional text log is emitted before termination. Exit does not run its own children, and an unfinished collected row is discarded.