01 / BROWSER · MEASURED RUN
The changing form.
Ten rows. Seventy fields. A form that shuffles after every submission. The saved workflow finds the fields by their labels and verifies the final score.
Interactive illustration. Sample data; no live submissions.
A different form. Every row.
Workflow illustration. This is a supported pattern, not a recorded production run.
70 of 70 fields.
10 rows completed.
Challenge timer1,735 ms
34.2 s · real time, no speed-up. A local batch is killed at row five, resumed, then run again.
WHAT GOES IN
challenge.xlsx
WHAT COMES OUT
10 submitted forms
THE CHECKS
- 10 rows processed
- 70 / 70 fields correct
- 100% final score
THE CONTEXT
The challenge has no per-row receipt. Its final score proves the complete batch; real business workflows need a check for each item.
Inspect the workflow Read the full use caseWhat exactly was measured?
- RPA Challenge’s own timer
- 1,735 ms
- Journal duration, including setup & checks
- 3,190 ms
- CLI wall-clock duration
- 3,559 ms
- Environment
- Windows · Node 24 · headless Chrome
One measured run, recorded 3 October 2026. The 18-second showcase is an illustration slowed down for readability; it is not a performance measurement.
Read the original measurements