Where to find the runs of a deployed workflow in Maestro, how to read the status and steps of each run, and where to see every error in one list.

Every run of a deployed workflow is recorded in Maestro, whichever tool you built and deployed it with. For each run, you can see how it started, which path it took, what each step received and returned, and how long each step took. Maestro keeps each run for 30 days after it ends.

If you deployed with a coding agent, ask it about your runs, for example:

The Process instances tab lists each run with its status, its name, the version of the workflow it ran, when it started and was last updated, how long it took, and who started it. In Maestro, a run is called an instance.

To start a run of a workflow without inputs, select Run at the top right. A notification confirms that the run is queued. Run doesn't ask for inputs, so for a workflow with inputs, use Start job instead. Deploy a workflow describes it.

To narrow the list, use the filters at the top: Version, Date range, Status, and Error message. When you select a single version, the workflow appears above the list.

Select the name of a run in the list. The run opens with:

Use the arrows next to the run's name to move to the previous or next run.

In the left panel of Maestro, select Flow incidents. The page lists the errors of all your workflows, with the workflow's name, its folder, the error message, how many times the error happened, and when it was first seen. When nothing has failed, the page says that there are no active incidents.

When a step fails, the run pauses at that step instead of ending. Its status is Faulted, the failed node is marked on the canvas, and the Incidents tab shows the error. The run waits until you retry or cancel it. Retry and cancel describes both.

Build the notification into the workflow. On the node that might fail, connect its error path to a step that sends a message, for example a Slack connector that posts to your team's channel, or an email. The message can include the error details, so whoever reads it knows what went wrong. Error handling describes error paths, and Handle errors shows the alert pattern step by step.