Branch on a condition you can check
Use conditions and If / Else blocks to choose a path. Labels, groups and repeat controls help organise sequences that have more than one outcome.
A practical pattern is to submit a test record, check for the expected confirmation and continue only when it appears. Handle a known error separately, and define what should happen if neither expected state is found.
Put limits around repeated work
Set loop limits and timeouts during setup. Use a Retry Block for a bounded retry where repeating the operation is appropriate, and configure Abort stop conditions for the states that should end the scenario.
Check whether an action already succeeded before retrying it. Submitting the same record twice is a different problem from retrying a screen lookup.
- Define the successful result before building the branch.
- Add a known-error path and an explicit timeout outcome.
- Keep the number of retries finite.
- Test the unsuccessful paths as well as the successful one.
Make the next review easier
Use clear action names and comments, and keep each branch focused on one decision. Add screenshots or configured alerts where they will help someone investigate a problem.
Conditional logic handles the situations you define. An unfamiliar dialog or an inaccurate OCR result still needs testing and an appropriate stop or review path.