Run Lists

• What is a Run List?
• Create a new Run List
  • Duplicate a Run List
    • Freeze a Run List
  • Import a Run List
  • Export a Run List
• Manage Run Lists
  • Search a Run List
  • Edit a Run List
  • Rename a Run List
  • Delete a Run List
  • Add steps to a Run List
  • Add flows to steps
  • Retry Policy for Run Lists
  • Get Run List ID

What is a Run List?

A Run List is a collection of one or more automation flows that are executed on one or more Schedules. Run List execution is managed by the Leapwork Controller. Common use cases include:

• Executing collections of flows against development or test environments

• Grouping flows into steps and controlling execution order

• Triggering business processes on a schedule

• Executing flows via the public REST API

• Running automation as part of CI/CD pipelines

• Running the same flows in different configurations or environments

After designing automation flows, users can create and schedule a Run List of flows to run automatically in different operating systems and browsers using the Scheduler configuration available under a Run List:

Create a new Run List

To create a new Run List, follow these steps:

1. In the Run Lists module, click the New button:
   
   
2. Choose the Run List option. 
3. Provide a name for the new Run List, e.g. 'TestRunList'. 
   
   

Duplicate a Run Lists

In order to manage the flows efficiently or to make multiple Run Lists with similar flows and settings, the user can create a copy of a Run List. Copying a Run List generates an entirely new version of the Run List and it's associated Schedules.

However, reference to the flows is maintained. So making changes in one Run List's steps or schedules will not impact the other one. If a flow is modified or deleted, the changes will be reflected in both Run Lists. Users can manually add/remove steps and flows in the copied Run List as needed.

In order to copy a Run List, do the following:

1. Navigate to the Run Lists section in Leapwork and right-click on the Run List that needs to be copied.
2. Choose the Copy option from the context menu.
   
   
3. Choose a folder and/or simply right-click in the blank area of the Run List section.
4. Select the Paste option.
   
   
5. A copy of the Run List is generated containing all steps/flows in the original Run List. The associated schedules are also duplicated. However, the schedule is disabled so that it doesn't trigger with the same settings i.e. Start Time and Agent:
   

Freezing Run Lists

Freeze Run Lists is a feature designed for DevOps and QA teams that require strict documentation, audit trails, and compliance, such as those working under GxP or similar regulatory frameworks.

To freeze a Run List, open it and click the Freeze Run List button in the Run List header.

When you freeze a Run List, you are locking both the list and its associated automation flows in their current state. This guarantees absolute version control and ensures that the configuration cannot be altered, providing a secure and auditable baseline for validation and compliance.

Freezing a Run List ensures that:

• Approved flows and configurations remain unchanged and tamper-proof.

• Teams can confidently reference locked flows during audits or validations.

• The configuration is secure, verifiable, and compliant with regulatory requirements.

• Only the exact, approved version is executed, even if newer versions of flows exist elsewhere.

What happens when you freeze a Run List?

• The Run List becomes permanently read-only, no further edits are possible.

• A lock icon appears next to the Run List name, both in the file explorer and in the Run List header, clearly indicating its frozen status.

• A timestamp and the name of the user who performed the freeze are displayed.

• The main action button changes to Duplicate (instead of Edit), allowing you to create a new, editable copy if changes are needed.

• All editing options (adding, removing, or reordering flows, changing parameters) are disabled.

• Tooltips and messages inform you that the Run List is frozen and only available for viewing, execution, or duplication.

• In the file explorer, additional icons may indicate the number of flows and the frozen state.

What can you still do with a frozen run list?

Even when frozen, you can:

• View the original version and its details at any time.

• Execute the frozen Run List as needed.

• Duplicate the Run List to create a new, editable version for further development or updates.

• Rename the Run List or its schedules (the content remains locked, but the label can be changed).

• Modify the steps, flows, or settings, but only in the duplicated (unfrozen) copy.

Note: You cannot “unfreeze” or revert a Run List to an editable state. Any changes must be made on a duplicated copy. This is a one-way, compliance-driven action.

Importing and exporting Run Lists

You can import and export Run Lists (or folders of Run Lists) as ZIP files. This supports migration, backup, and sharing across environments.

Import Run Lists

Import Run Lists or folders from a previously exported ZIP file, preserving the original folder and flow hierarchy during the import process.

To import a Run List or a folder of Run Lists, right-click within the Run List panel and select Import or Import as Folder from the context menu. In case of conflicts (e.g., duplicate IDs or names), you can choose:

• Update existing items
• Save as new
• Cancel
  

Note: If a frozen Run List is included, it will be skipped during import and a message will appear

"Runlists that are currently in a frozen state will not be updated."

Note: Import actions such as Create Runlist, Update Runlist, or Create Schedule are also recorded in the audit log with the context marked as Imported.

Export Run Lists

• Export individual Run Lists or entire folders.

• Includes folder structure, flows, schedules (if any), and an Excel file summarizing metadata.

• A pop-up window allows you to define the ZIP file name and destination.

• Once the export is complete, a confirmation message will appear to indicate the operation was successful.

To export a Run List or folder, right-click on the target item and choose Export or Export As Folder from the context menu.

Note: Export actions (e.g., "Export Runlist") are recorded in the audit log with the context marked as Exported.

Manage Run Lists

Search a Run List

To search for a Run List, use the search bar located at the top of the Run List module or within the file explorer. Simply enter the name or part of the name of the Run List you are looking for. The system will instantly filter and display matching Run Lists, making it easy to locate the one you need.

When searching, the icon of the Run List that matches your search will be highlighted in green, allowing you to quickly identify the specific Run List in the results. You can also use advanced filters to narrow your search by status (such as frozen), owner, or other attributes.

Edit a Run List

To edit a Run List, double-click on its name in the Run List module or use the right-click context menu and select Edit. This will open the Run List in edit mode, allowing changes to its name, steps, flows, retry policy, or other configurations.

Rename a Run List

To rename a Run List:

• Right-click the Run List and select Rename, or press F2 when selected.

• Enter a new name and press Enter.

Delete a Run List

To delete a Run List:

• Right-click the Run List and select Delete, or press Del.

• Confirm the deletion in the prompt. Note: associated schedules will also be deleted unless removed manually beforehand.

Add steps to Run Lists

A Run List always consists of one or more steps. Each step in a Run List can contain one or more flows to be executed. Users can add multiple steps to define and control the execution of the flows. The first step is always executed and the rest of the steps can be made conditional, i.e. their execution can be controlled on the basis of the outcome of the previous step. 

There are four available conditions to choose in the 'Step':

In order to add steps to the Run List, do the following:

1. To add steps to a Run List, you can use any of the following options:

1. 1. There is an Add step button available before and after each step. Click this button to insert a new step in that position.
      
      

   2. You can also hover between two existing steps: a “+” icon will appear in the gap, allowing you to quickly insert a new step exactly between those steps.
      
      

2. Once the button is clicked, a new step will be inserted as shown below:
   
   
   
3. Once the Run List is ready, the user can bind it to a particular schedule for autonomous execution.

Add flows to Steps

In order to add flows to the steps, do the following:

1. Click the Add flows button in the corresponding step where you want to add flows:
   
   
2. A popup window will open that shows all of the available flows. Users can select one or more flows by pressing the Ctrl button and clicking on the corresponding folder/flows.
3. The Add button will be enabled on the popup after the user selects one or more flows. Users should click on the button in order to add the selected flows to the step:
   
   
4. After adding the flows, the step will list all of the selected flows:
   
   

Retry Policy for Run Lists

Each Run List includes a Retry Policy setting accessible via the Retry Policy button in the top menu. This setting defines how Leapwork handles failed flows in this Run List.

The options are:

• Do not retry failed flows for this run list 

• Use default retry settings: Inherit from global configuration

• Customize retry settings for this run list: Define a specific retry count between 1 and 5 retries; this is the minimum and maximum allowed range.

  
  
  

Retry settings apply only to flows within this Run List and can be overridden by Retry Policies defined at the Schedule level. Retry configuration is preserved during export/import.

Get Run List ID

Right-click the Run List and select Get ID to copy its unique identifier to the clipboard. The ID is automatically copied to your clipboard for use in APIs, debugging, or integrations.

Note: No confirmation message is shown, but the behavior is equivalent to copying text using Ctrl+C.