Concurrency and repetitions

A concurrency of 10 and 100 repetitions means 100 runs in total, with no more than 10 running at once. Each run starts at the first action and gets its own variables, lists, tables, profile and cookies. Only initial values explicitly saved in the project are restored; changes from a previous repetition are not inherited.

The runner stores the completed repetition count on disk. After 1,000 of 10,000, 9,000 remain. An interrupted repetition restarts from the beginning; completed ones are not repeated. Paused and stopped states survive a service restart. Explicit writes to external files and databases remain.

New runs wait if access has expired or the project lacks allocated workers or memory. Waiting does not consume a repetition. Running tasks may finish within their current authorization. External writes may have occurred before an interruption, so your project must handle retries of those operations safely.