- Getting started
- Administration
- Designing automations
- Creating an automation from an idea
- Creating a project
- How to start an automation
- Managing project files and folders
- Connecting automations to your accounts
- Configuring activities
- Managing the activities in a project
- Passing values between activities
- Iterating through items
- Managing the data in a project
- Configuring a project to use your data
- Using file and folder resources
- Using UI Automation for browser interactions
- Running and testing your projects
- Running a project
- Viewing the run output
- Publishing a Project
- Managing automations
- Studio Web API
Running a project
You can test your projects by running them directly from the workflow designer.
Projects run on the robot type selected for your account. By default, automations run on Automation Cloud™ - Serverless robots. For more information, see unattended robot setup.
You can also use your local machine to run your projects by expanding the drop-down menu next to the testing button and selecting the On local machine or On cloud options.
Note that testing locally requires you to install and run UiPath® Assistant 2024.10.5 or newer. If UiPath Assistant is not installed on your machine, you are prompted to download it when you choose to test on your machine. You also need to be signed in to Assistant and Studio Web using the same user name and within the same organization and tenant.
The options for running a project are:
-
Test on cloud or Test on local machine - The entire project is run, starting with the main workflow. When you run the project, you can select Stop to stop the execution and return to the project.
Tip:If you want an automation to pause before a certain activity, add a breakpoint to that activity. For example, you may want to check the results of the steps in a workflow up to a certain point before continuing with the execution. To add a breakpoint, select Actions
> Add
breakpoint for that activity.
When the breakpoint is reached, the workflow pauses, and you can either stop execution, continue running the rest of the workflow, or continue running the workflow step by step.
As the project runs, an hourglass icon is displayed at the top of the activity that is currently executed. The icon turns to a green checkmark when the activity was run successfully. If an error occurs when executing an activity, execution stops, a red error icon is displayed at the top of the activity, and the activity header is also highlighted in red. Hover over the icon to see the error message with the cause of the error.
-
Test step-by-step - The project runs one activity at a time, starting with the main workflow, allowing you to validate each step along the way. The following options are available when you run step-by-step:
- Stop - Stops the execution and returns to the project.
- Continue - Runs all remaining steps or until the first breakpoint is reached.
- Next Step - Runs only the next step.
In projects that contain multiple workflow files, Test and Test step-by-step run the main workflow regardless of the workflow you are currently working on.
To debug a specific workflow in your project, right-click the workflow file in the Project explorer and select:
- Test workflow to run the entire workflow.
- Test workflow step-by-step to run the workflow one activity at a time.
When you're testing a project step by step, you can follow the values of variables,
arguments, and expressions as the workflow runs by selecting Open watches panel
on the right of the workflow
designer. Watching values can be helpful in identifying potential issues.
Variables and arguments are automatically added to the watches. You can expand the entries for variables and arguments that have multiple properties to view the values of the available properties.
To add a watch:
- Select Open watches panel
on the right of the project page.
- Type a value in the provided text box and press Enter. As you start typing, autocomplete suggestions are displayed.
UipathEvent or
UipathEventObjectType) are not displayed as local variable values in the
Watches panel. However, these values are available in the Expression Editor.
If you are using an Orchestrator event trigger to start an automation (as opposed to a trigger which is explicitly set in the workflow), you can only access its event trigger data in the Expression Editor. To learn more about Orchestrator triggers, see the Orchestrator guide.
