What the most common Maestro Automate errors mean, and how to fix them in the workflow or with help from your administrator.

Most errors come from how a node is set up, and you can fix them on the canvas yourself. A few come from how your company's UiPath account is set up, and only an administrator can fix those. Find the message you see below.

When a run fails in debug mode, the failed node turns red and the Incidents tab shows the message. Debugging basics describes where to look.

A required field on the node is empty. Select the node and fill in the fields marked as required before you test the workflow.

The workflow has no trigger, so nothing can start it, and Debug stays unavailable. Add a trigger, such as a Manual Trigger, and connect it to the first node. Triggers lists the options.

A field set to Expression holds plain text, such as a URL, without quotes, so it's read as code. Do one of the following:

Expression syntax explains the two field modes.

The expression points to a node or a field that doesn't exist, usually because of a typo. A common case is a name entered twice, such as productIdproductId: the editor suggests the name as you type, and typing it as well adds a second copy. Node IDs can differ from the names you see on the canvas, for example httpRequest1. Instead of typing the reference, select it from the Insert menu next to the field label, which lists only values that exist.

The expression reads a field of a value that is empty. This happens, for example, when an earlier node returned nothing. Check the earlier node's output in the execution trace, and make sure it returns a value. To allow an empty value, use optional chaining, for example $vars.getOrders.output?.length. Expression syntax describes it.

The full message reads: "Integration Services operation failed. Unified HttpRequest failed with status code '502', message: Name or service not known". An HTTP Request node can't reach the address in its URL, usually because the host name is wrong. Check the URL for typos, and open it in a browser to confirm that it responds. If the failure happened in a deployed run, fix the URL, deploy again, then retry or cancel the failed run as Retry and cancel describes. HTTP Request describes the node's fields.

The workflow calls an API workflow that isn't deployed yet. Deploy the API workflow first, then test again. Maestro Automate or API workflow describes how the two work together.

Expression syntax: Common errors covers errors such as undefined values, conditions that behave unexpectedly, and values that aren't available to a node.

Some problems come from how your company's UiPath account is set up. Send your administrator the exact message and a link to Administration, which lists what they need to turn on.

If you signed up yourself, your account is ready to use and you don't need an administrator. Sign up describes what's included.

Sign-in, CLI, and deployment problems that are specific to VS Code are covered in VS Code extension: Troubleshooting.