Run the flow

Run the deployed Price Watch Flow in Orchestrator, review the job trace, and clean up the resources created in this tutorial.

Step 6 - Running the Flow with Orchestrator

After opening the deployment using the "View deployments" from Step 5, follow these steps to run the Flow inside your UiPath Automation Cloud account:

1. Expand the "Shared" folder.
2. Select the tutorial-maestro-flow-price-watch folder under "Shared".
3. Use the Start job button for the tutorial-maestro-flow-price-watch deployment to open the "Start Job" dialog.
4. Use the Start button to start the job - the input values will already be set to the default values of USD, EUR, and 0.9.
5. Verify the output values for watchResult when "✅ Successful" shows the job has completed.
6. Open the Trace tab to view each of the steps and the time each step took to execute.

Congratulations! You've completed your first Maestro Flow by building, testing, deploying, and then running it! Before you close this page, make sure to follow the last step to clean up the resources we deployed in this tutorial.

---

Step 7 - Cleaning up the resources

Now that you've completed the tutorial, you can continue to modify it, or remove the resources that we created for the tutorial-maestro-flow-price-watch deployment. For the cleanup, we need to remove the following resources:

• The Automations Process the deployment created
• The deployment
• The published package
• The two folders under Shared (one for the deployed version, the second created when executing the Flow with Debug)

A deployment into a Shared folder is fully managed from the CLI, and we use CLI commands from the terminal in VS Code to clean up items 1, 3, and 4. To remove the deployment (item 2), we will use Orchestrator in your UiPath Cloud account. In the steps below, we will use both the uip solutions and uip or (or for Orchestrator) CLI commands. To remove all the resources, follow the following steps:

1. Run the command below to uninstall the deployment - this deactivates the deployment, and removes the Automation Process and the folder it was deployed to.

   uip solution deploy uninstall tutorial-maestro-flow-price-watch --yes
   

   The result should be similar to:

   {
       "Result": "Success",
       "Code": "SolutionDeployUninstall",
       "Data": {
           "Status": "SuccessfulUninstall",
           "DeploymentName": "tutorial-maestro-flow-price-watch",
           "InstanceId": "abcdef12-3456-7890-abcd-ef1234567890_v7"
       }
   }
   

2. Run the command below to delete the published package:

   uip solution packages delete tutorial-maestro-flow-price-watch 1.0.0 --yes
   

   The result should be similar to:

   {
       "Result": "Success",
       "Code": "SolutionPackagesDelete",
       "Data": {
           "PackageName": "tutorial-maestro-flow-price-watch",
           "PackageVersion": "1.0.0"
       }
   }
   

   Tip:

   If you used different versions, or deployed multiple times with VS Code, you can use uip or packages versions tutorial-maestro-flow-price-watch.flow.PriceWatch --output table to list all the versions. Use the command from above with each of the version numbers you see: uip solution packages delete tutorial-maestro-flow-price-watch <version number> --yes.

3. Retrieve the Key of the folder you deployed to with:

   uip or folders list --limit 200 --output-filter "[?contains(Path, 'Debug_tutorial-maestro-flow-price-watch')]"
   

   The result should be similar to:

   {
     "Result": "Success",
     "Code": "FolderList",
     "Pagination": {
       "Returned": 3,
       "Limit": 200,
       "Offset": 0,
       "HasMore": false
     },
     "Data": [
       {
         "Key": "aaaaaaaa-bbbb-cccc-dddd-1234567890ab",
         "Name": "Debug_tutorial-maestro-flow-price-watch",
         "Path": "Shared/Debug_tutorial-maestro-flow-price-watch",
         "Description": "",
         "Type": "DebugSolution",
         "ParentKey": "11111111-2222-3333-4444-abcdef123457"
       }
     ]
   }
   

4. Delete the folder using the value from the Key field above (replace aaaaaaaa-bbbb-cccc-dddd-1234567890ab with your value).

   uip or folders delete aaaaaaaa-bbbb-cccc-dddd-1234567890ab --yes
   

   The response should look similar to:

   {
     "Result": "Success",
     "Code": "FolderDelete",
     "Data": {
       "Key": "aaaaaaaa-bbbb-cccc-dddd-1234567890ab",
       "Path": "<your email>'s workspace/Debug_tutorial-maestro-flow-price-watch",
       "Status": "Deleted successfully"
     }
   }
   

5. In your UiPath Cloud tenant, navigate to Orchestrator, select the Solutions tab.

6. Open the context menu for the inactive tutorial-maestro-flow-price-watch deployment and use the Delete option to delete it.

   

Congratulations! You've now completed this tutorial, and cleaned up all the resources created as part of it. Below are links to additional tutorials and content for you to continue building on UiPath.

---

What's next

• Getting Started with UiPath Agents - build a low-code agent from the CLI, the component an Agent node drops into a flow.
• Adding Tools to Your UiPath Agent - configure an HTTP request against a public API from the API Workflow side, and compare it with the HTTP Request node in this flow.
• Building a Low-Code Agent in Studio Web - the same agent contract, built on the browser canvas in 20 minutes.
• Getting Started with UiPath Agents using LangGraph - move from configured components to coded ones with the Python software development kit (SDK).
• Flow in VS Code - the full extension reference, including keyboard shortcuts and settings.
• UiPath Community - forums, how-tos, and developer discussion.