Skip to main content

Running & monitoring

A run is one execution of a workflow. This section covers how runs start, how to watch them, and how to review what happened.

How a run starts​

A run is created when a workflow is triggered. Triggers include:

  • Test Run — you start it manually in the builder, with sample data.
  • Webhook — an event in a connected platform (like a new WooCommerce order).
  • Schedule — on a cron-based schedule you define.

Runs are asynchronous​

When a workflow is triggered, OrchaSync queues the run and works through it in the background. Runs are processed per company, so one company's activity never blocks another's. You don't need to keep a browser open for a run to complete.

What you can see​

Every run records a step for each node it executes — what the node received, what it produced, and any error. You can:

  • Watch live during a test run as nodes light up. → Test runs
  • Review afterward in the run history. → Run history

Run status​

A run moves through a small set of statuses:

StatusMeaning
QueuedThe run is waiting to be picked up.
RunningThe run is executing.
SuccessThe run finished without error.
FailedA step errored and the run stopped (unless an Error node handled it).