Breadcrumbs

Recording or running sequences

I am trying to start the recorder, however I cannot seem to click on the “Start recording” button. How do I proceed?

  • Check if the certificate is trusted.

    • Open certmgr.msc

    • Navigate to Trusted Root Certification Authorities → Certificates

    • Confirm the Leapwork Performance certificate is listed

    • If missing, reinstall the certificate into this location

    • Fully restart your browser afterwards

  • Make sure that your proxy is turned OFF

  • Perform performed a hard refresh (Ctrl+Shift+R or Cmd+Shift+R) of the Performance domain starting

My recording only appears after disconnecting proxy. Is that expected?

Yes, this is expected. Performance cannot finalize and fetch events until the proxy disconnects.

I turned on the proxy extension, and turned on the Recorder. Upon ending my recording, nothing is saved to my sequence. What do I do?

If you start a recording but no steps appear in the sequence, work through the steps below.
Most recording issues are resolved by one of these checks.

Step 1) Check the Performance certificate

Performance requires its certificate to be trusted in order to capture HTTPS traffic.

Steps:

  • Open certmgr.msc

  • Navigate to Trusted Root Certification Authorities → Certificates

  • Confirm the Leapwork Performance certificate is listed

  • If missing, reinstall the certificate into this location

  • Fully restart your browser afterwards


Step 2) Restart the browser completely

Performance will not capture traffic until the browser has fully reloaded its trust store.

Steps:

  1. Close all browser windows

  2. Ensure no background browser processes (Chrome/Edge) are still running

  3. Reopen the browser and reconnect the proxy


Step 3) Verify proxy configuration

Recording requires the proxy to be correctly configured in the browser extension.

Check:

  • Protocol: HTTP (not HTTPS)

  • Port: 8080

  • Status shows “Connected”

  • No OS-level proxy or VPN overwriting settings

If websites stop loading when the proxy is ON, the proxy settings are incorrect.


Step 4) Use two different browsers

Performance and the application under test should not run in the same browser.

Recommended:

  • Browser A: Performance (e.g., Chrome)

  • Browser B: Your application + proxy extension configured to the Performance recorder (e.g., Edge)

This ensures all test traffic goes through the proxy without interfering with Performance itself.


Step 5) Hard-reload the application page

Some applications use caching or service workers.

Use a hard reload:

  • Windows: Ctrl + Shift + R

  • Mac: Cmd + Shift + R


Step 6) Disable other proxy tools

Other tools may intercept traffic and block Performance from capturing it.

Temporarily disable:

  • Fiddler

  • Charles

  • BurpSuite

  • Corporate SSL-inspection tools

  • VPNs with traffic interception


Step 7) Ensure extension permissions are granted

The proxy extension must be allowed to access all sites.

Steps:

  1. Go to browser extensions

  2. Open the proxy extension

  3. Enable “Allow access to all sites”

I went to turn on the proxy extension to start recording, and it is asking for a username and password. What do I type?

Sometimes, the proxy extension will prompt for credentials. To resolve it, you need to paste the key into the password field. You can resolve it by following these steps:

  1. Go to Performance

  2. Locate your profile avatar in the top right corner

  3. Click on the avatar, and then click on the key in the dropdown to copy it.

  4. Paste it into the password field.

  5. Leave the username blank

  6. Click "Sign in".

The number of generated transactions by Performance doesn’t match the number I expected. Why?

Performance works by simulating users performing a set of similar actions (the designed sequences) concurrently. While Performance will certainly generate the necessary network traffic and actions to simulate it, some systems don’t always act as expected when this sort of load is applied.

As a result, mismatches can occur. Simply because all users are hitting same ID at the same time. It is important here that as you scale load, you don't expect the application under test to always behave similar to 1 user doing it. This is where you can discover unwanted behaviors.

How do I run a test from different regions?

For a Sequence

Find your desired Sequence, and click on it. Once opened, you will see a dropdown next to Record button. Open that dropdown to see the regions that are available for you to select between.

For a Timeline

Find your desired Timeline, and click on it. Once opened, you click on the relevant sequence. That will bring up the configuration panel, and in the “Geographic distribution” panel, you choose your desired region from the Geographical location dropdown (e.g., East US, North Europe, Southeast Asia).


Performance spins up agents in those cloud regions automatically and displays the latency differences live.