Skip to content
LogoLogo

Running and monitoring

Run a workflow

Open a published workflow whose canvas matches the published version. The button reads Run workflow. Fill in the Trigger's inputs and start it.

You need Editor on the workflow to run it.

Run states

StateMeaning
RunningSteps are executing.
WaitingPaused on an approval or a Wait step. Survives restarts and deploys.
CompletedFinished.
FailedA step failed and was not handled, or the run hit its timeout.
CancelledSomeone stopped it.

Each step has its own state too: pending, running, succeeded, failed, waiting, or skipped (its branch was not taken, or it is set to Skip).

When a step fails

Loading diagram...
ControlWhereUse for
Retry on failStep โ†’ SettingsFlaky APIs and rate limits. 2โ€“10 tries, 0โ€“30 s apart.
Error outputStep โ†’ Settings โ†’ On errorHandling a known failure: a guardrail block, a 404, a rejected record. You must connect the error port.
Continue on errorWorkflow settingsBatch jobs where one bad item should not stop the rest.
Stop & ErrorA stepFailing deliberately with a clear message.

Cancel

Stop a run from the builder's top bar or Runs view. Cancelling stops further steps; it does not undo actions already taken. Child runs started by Execute Workflow are cancelled by cancelling the parent.

Watching runs: workflow traces

Sidebar โ†’ Traces โ†’ Workflows tab.

ListDetail
Workflow, started, trigger (Manual, Schedule, Child of workflow), duration, status. Filter by status, workflow and time window (last hour to all time). Search by workflow or run id. Select runs and Download JSON.Timeline and Tree views of every step, step search, and each step's input and output items. It shows the exact published version that ran.

Workflow trace detail in Timeline view, with the AI Agent step selected to show its output items

An AI Agent step also produces a normal agent run, with its own step waterfall in the agent Audit traces.

Reliability

  • Runs are durable. Waits, approvals and in-progress steps survive restarts and deploys.
  • A background sweep repairs runs that were interrupted, for example a run saved but never started, or an approval answer that did not reach its run.
  • A step that crashes part way is retried by the engine. A step that calls an outside system may therefore occasionally run twice; prefer actions that are safe to repeat.

Limits

LimitValue
Run timeout (active time)1 hour default, up to 24 hours
One step5 minutes
Steps running at once in a run10
Items a step processes at once5
Loop passes1,000 by default
Workflow nesting5 levels
Retries per stepUp to 10 tries
HTTP Request30 s, 5 MB, 5 redirects
Approval50 users, 20 groups, 20 roles, 6 decisions, 20 fields
ScheduleEvery minute at most

What gets recorded

EventAudit action
Create, rename, edit the graphworkflows.create, workflows.update, workflows.graph.update
Publish, pause, resume, deleteworkflows.publish, .pause, .resume, .delete
Start or cancel a runworkflows.runs.create, workflows.runs.cancel
Answer an approvalworkflows.runs.resume
Bind or unbind an app accountworkflows.toolkits.bind, .unbind
Share or unshareresources.share, resources.unshare

Scheduled runs and edits made by the Workflow assistant are recorded too, attributed to the person they act as.

Troubleshooting

SymptomCheck
"Publish this workflow before running it"It has never been published. Publish, then run.
Publish refusedRead the listed problems: unconnected error ports, missing models, a disabled step, an unsupported expression such as $node[โ€ฆ].
Schedule never firesWorkflow is Active, the schedule is enabled, you republished after changing it, and the publisher is still a member.
If step fails with a missing pathThe field is not on every item. Use is empty or fix the path.
Far more actions than expectedFan-out. Check item counts in the Logs drawer; add Limit, Filter or Aggregate.
Run stuck in WaitingAn approval nobody answered. Check the Approvals page and the notification settings.