Skip to content

Guides

Check an execution & find errors

You find out why a workflow or agent run failed and fix the cause in the workflow.

A failed or suspicious run is understood. The cause is fixed in the workflow, in the agent or in the data.

AI & automation owner, Admin.

  • There are runs, for example from Workflows, agents or Polaris background work.
  • You see your own runs. Admins see all runs of the organization. The inputs and outputs of the steps are visible only to the run’s owner and admins.
  1. Open executions – the page Ausführungen (/executions), e.g. via a workflow run in the Polaris sidebar. On the left is the list of runs, newest run at the top. Without your own selection, Aligia opens the most recent failed run.
  2. Classify the run – The header shows workflow name, kind („Rules“, „Agent“ or „Chat“), status, revision, time, duration, step count and trigger source („Manual“, „CDC“ or „Chat“). „child failed“ marks runs whose child run failed, even if the main run appears successful.
  3. Follow child runs – Under „Children“ is the tree of child runs, such as workflows started by rules or subagents. Select the failed branch.
  4. Find the step – For workflow runs, „Regeln“ (Rules) shows each rule with status and duration; „bei Regel …“ (at rule …) names the failed one. The „Step trace“ lists all steps with status and duration. The failed step is already expanded and scrolled into view. It shows „Input“ and „Output“ with the error message. For agent runs, the „Transcript“ shows the dialog and the tools called.
  5. Identify the cause – The strongest hint is the error message in the „Output“ of the failed step. Other typical causes are rejected tool calls in the „Transcript“, an unreachable MCP server or a reached step limit („ceiling reached“).
  6. Share or analyze – „Export“ downloads the run as „JSON“ or „AI digest“. You can give the digest to Polaris for analysis.
  7. Adjust the workflow – Ask Polaris to correct the workflow. For an enabled workflow this creates a proposal; it only applies once the owner or an admin accepts it.

The cause is known and fixed. The next run appears again in the Executions.

Build & trigger a workflow · Triggers