EXCEL + PARALLEL BROWSERS

Process Excel Work in Parallel Browser Sessions

Give each independent spreadsheet row its own browser page, then merge the outcomes into one controlled local report.

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.

  • Download account, order, status, and note data from a real Excel workbook.
  • Create one independently owned webpage object for each parallel iteration.
  • Sign in, update the assigned order, and verify the visible save result through CDP commands.
  • Protect the shared result list with a lock before writing a consolidated Excel report.

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.

Load work from Excel

The application monitors the browser download, retrieves the .xlsx path, and converts each non-header row into an independent work item.

Start a parallel list loop

Runavelo assigns each work item to a separate iteration. Every iteration opens and owns its own vendor page instead of relying on whichever tab is active.

Authenticate and target one order

Stable CSS selectors locate login controls and an order-specific select, note field, and save button derived from the spreadsheet order ID.

Capture results safely

Each page reads its visible status. A lock protects the shared result list so concurrent iterations cannot corrupt the consolidated output.

Close pages and write the report

Each iteration closes its webpage after verification. The completed result list is written to a user-relative workbook and the full path is logged.

EXPECTED OUTPUT

Evidence you can inspect after the run.

  • A workbook named parallel-browser-results.xlsx in Documents\Runavelo Demo Results.
  • One row per account and order, including the requested status and the page-confirmed result.
  • Runtime logs containing the actual downloaded input path and the consolidated output path.
  • 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.

Does parallel execution always make a workflow faster?

Only when tasks are independent and the website permits concurrent sessions. Reduce concurrency for ordered work, shared state, or strict rate limits.

Can each row use a different website?

Yes. Include the authorized destination URL in the input data and pass it to the Open Webpage command, while validating the allowed domains before execution.

TRY THE COMPLETE AI PATH

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.