Define independent work items
Each item contains its own credentials, order identifier, target status, and note, preventing state from leaking between sessions.
PARALLEL BROWSERS
Run Parallel Browser Sessions from One Computer
Process independent vendor portal records concurrently while each iteration owns its page, login data, update values, and verification result.
WHAT THE AI WILL BUILD
A real visual workflow, not a conceptual diagram.
The AI guide supplies a precise goal, safe target page, inputs, output contract, and verification rules. Paste that prompt into Runavelo's built-in assistant, then inspect and edit every generated command before execution.
- Start three independent webpage contexts from a parallel list loop.
- Sign in with isolated fictional vendor credentials.
- Update a different order status and note in each browser session.
- Verify and log the result inside the iteration that owns that session.
Responsible use: adapt this pattern only for systems and data you are authorized to automate.
WORKFLOW WALKTHROUGH
How the visual workflow operates.
Each stage has a specific input, browser context, output, and verification point. Edit these commands directly when the destination system differs.
Open one page per iteration
The parallel loop opens and retains a separate webpage object for each vendor session.
Sign in through CDP controls
Email and password fields receive CDP silent input, followed by a CDP click on the sign-in action.
Update the assigned order
The current session selects a status, enters its note, and saves the record without borrowing another iteration's webpage object.
Verify locally, finish globally
Each iteration reads and logs its portal status. A final message appears only after all three parallel items have finished.
EXPECTED OUTPUT
Evidence you can inspect after the run.
- Three independently updated demo vendor orders.
- A status message captured from each browser context.
- A final log confirming that all parallel iterations completed.
Runavelo's runtime log connects the visible workflow line to its result. That makes missing elements, rejected updates, and unexpected page states easier to locate than a generic success message.
COMMON QUESTIONS
What to change for a real workflow.
Is this the same as opening tabs manually?
No. Each parallel iteration owns a distinct webpage object and data item. The design prevents commands from accidentally targeting whichever tab happens to be active.
Should every workflow run in parallel?
No. Use parallel execution only for independent work. Sequential processing is safer when records share state, must run in order, or the target system limits concurrency.
Copy the goal, let AI build, then inspect and run.
The prompt targets the matching test page and states the expected evidence. A reference QYA remains available for comparison with a verified implementation.