Direct answer

A run waits for eligible workspace capacity, then executes on one worker.

Manual and scheduled runs enter the same pending queue. The dispatcher checks workspace, project, and job concurrency plus worker capability before assignment.

01

During execution

The worker receives test files, project identity, base URL, and runtime variables. Playwright actions, logs, results, and artifacts stream back to the project run view.

02

At completion

The run settles as passed, failed, or error. Lifecycle acknowledgements protect assignment ownership during reconnects, while host-process loss and arbitrary external side effects are not presented as exactly-once guarantees.

EARLY ACCESS

Bring browser operations into focus.

Join the waitlist