LogoDrowUp Guide
Browser and RPA

RPA First Run

Choose a script, configure one environment, and safely check your first automated browser task.

RPA performs repeatable browser steps for you. Your first goal is not speed. It is proving that one script works with one store and one product.

Prepare the desktop client

Before starting, confirm all three items:

  • The DrowUp desktop client is open.
  • The intended fingerprint environment starts and is signed in to the correct store.
  • The local task queue is available.

If the local queue is unavailable, DrowUp may create a cloud task record without starting the real local browser work.

Choose a script

RPA Script Market with platform filters and available scripts

  1. Open the Script Market.
  2. Filter by the target platform.
  3. Read the script description and confirm that it matches the job.
  4. Install the script when required.
  5. Select Run Now.

Configure the first run

RPA run panel with concurrency set to one

Select an environment, select a product when required, and set concurrency to 1 before the first run.

  1. Fill the script's required settings.
  2. Select exactly one fingerprint environment.
  3. Select one product when the script needs product data.
  4. Set Concurrency to 1.
  5. Leave Close Browser When Finished off so you can inspect the final page.
  6. Turn Remember Configuration off when the current values are only for a temporary test.
  7. Check the target store and environment again.
  8. Select Run Now and keep the desktop client open.

Concurrency controls how many environments can work at the same time. A value of 1 makes the first run easier to watch and stop.

Remember Configuration may be enabled by default. Keep it enabled only after the settings have been checked and are useful for the next run.

Watch the browser and verify the result

The browser may open pages and fill or read content while the task is running. Do not treat an opened page as proof of success.

Example page reached while checking a local RPA run

After the task finishes, inspect the target store or page and confirm the expected change. Also review any output file or task message produced by the script.

Check before increasing concurrency

Increase concurrency only after the same script has completed correctly several times with one environment. Higher concurrency does not fix an incorrect script setup.

Next: Review results and solve common problems.