Running a project

You can test your projects by running them directly from the workflow designer.

There are two options for running a project:

• Test - The entire workflow is run. When you run the workflow, 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 workflow runs one activity at a time, 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.

You can view details about the progress of each run in the Run output panel.

Tip: To make it easier to follow the progress of the execution and view information about the outcome of activities, add Write Line or Log Message activities at certain points in your projects. These activities display messages in the Run output panel and can be configured to include the output of previous activities in the messages. For example, in a project that contains a number of activities that process a spreadsheet, you can add a Write Line activity after the last of the activities and configure it to display the message Finished processing FileName where the file name can be populated dynamically using the output of a previous activity that retrieved the spreadsheet.

Watching variables when testing a project

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:

1. Select Open watches panel on the right of the project page.
2. Type a value in the provided text box and press Enter. As you start typing, autocomplete suggestions are displayed.

Internal trigger event values (such as 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.