If a step fails because a page or element is slow, adjust the waits in the test case's Configuration panel (right side of the test case) under Wait and retries:

These default to your organisation's values ("Org Level") and can be overridden per test case. Prefer raising the locator wait over adding fixed wait steps — fixed waits slow every run.

In the same Configuration panel, Device Setting controls the Default Browser (e.g. chromium) and Default Viewport (e.g. 1280×720) for the test. Key Flags below it toggle Mobile Testing, Extension Use, and Data Driven mode.

The AI Configuration section of the panel controls AI Smartness, the default AI action, the Knowledge Base default for the test, and AI metadata collection — each inheriting from the organisation level unless overridden.

To run the same flow with different data sets: manage your data under Environment & Data → Data Profiles, then in the test case's Configuration → Execution set the Test Data Profile and Test Data Set, and enable the Data Driven key flag. In your steps, set the value's test-data type to Parameter so it reads from the data set. For values that differ per environment (URLs, credentials), use the Environment test-data type instead — see our article on test data and environments.

Each step row has a checkbox on the left — select multiple steps to act on them together, and use Reorder (top right of the steps list) to rearrange. Search Action Text finds a step in long tests.

If something looks broken rather than confusing — a toggle that resets, a button that does nothing, a step that won't save — tell support it's a bug report and include your workspace URL and a screenshot. That routes it to the engineering queue instead of a documentation answer.