Answers to common questions about Maestro Automate, each with a link to the page that covers the topic.

Maestro Automate is a product for building workflows in which AI agents and APIs work together. What is Maestro Automate? describes it.

In Studio Web, in your browser, with nothing to install. VS Code and Studio Desktop are also available. Where to build compares the three.

No. Studio Web runs in the browser. Where to build describes the environments that run on your computer, if you prefer one.

Yes. In VS Code, a coding agent such as Claude Code, Codex, Cursor, or Copilot can write the workflow file. In Studio Web and Studio Desktop, Autopilot (Preview) can build the workflow from a description. Build in VS Code describes the VS Code setup.

Your first workflow builds and debugs the order intake workflow in about 15 minutes.

At least one trigger. Triggers describes the trigger types.

Per run. Building, testing, and evaluating are free, and every plan includes a number of runs each month. Pricing lists what each plan includes.

A run can last up to 24 hours, and it's kept for 30 days after it ends. The agents and other work it calls, their traces, and audit events have their own retention settings, the same as in Maestro Orchestrate. How long run data is kept describes them.

Yes. A run that failed at a step can be retried from that step, and any run can be canceled. Retry and cancel describes how.

Up to 50. Limits and fair use lists the limits.

In debug mode. Select Run Debug (▶) in the bottom toolbar, and the execution trace shows what every step received and returned. Debugging basics describes how to read a run.

Yes, with evaluations. Evaluations describes datasets, evaluators, and runs.

With a Quick Form node, from the Human category. Add human approval to a workflow builds a complete example.

Yes, as nodes. A workflow can call RPA workflows, agents, API workflows, and Business Process Model and Notation (BPMN) processes. Call existing work lists them.

Yes, with guardrails on the agent node. Autonomous Agent describes them.

In a deployed workflow, the run pauses at the failed step and waits for you to retry or cancel it, as Retry and cancel describes. To let the workflow handle the failure on its own, connect the node's error path to other steps. Error handling describes how.

Start in Maestro Automate when each run finishes within 24 hours. Start in Maestro Orchestrate when the process waits days for a human or an event, someone must act on runs in progress, or it needs the BPMN or Case canvas. Maestro Orchestrate or Maestro Automate? compares the two products.

Yes, and converting is optional. The workflow isn't rebuilt, and you can convert it back. Convert to Maestro Orchestrate describes when to convert and what changes.

No. Audit events are captured the same way in both products. The difference is the run itself, which Maestro Automate deletes 30 days after it ends. How long run data is kept describes the retention settings for each part of a run's data.