Monitor workflow runs

Every time a workflow fires — automatically or by hand — Nash keeps a record of it. Execution History is where you go to see that record: every run, what it touched, and what happened at each step.

Open Execution History

From the workflow editor, open Execution History to see every run of that workflow, most recent first. Each row shows when it ran, what it touched, how long it took, and its status.

Run statuses

A run's own status — shown on its row in Execution History — tells you where it stands at a glance:

• Success — finished, everything ran as expected.

• Failed — finished, but hit an error.

• Running — still in progress.

• Paused — waiting before it continues (for example, ahead of a delayed action) — it picks back up on its own.

• Cancelled / Pending — stopped before finishing, or not yet started.

Open a run and each individual step inside it carries its own status too:

• Passed — the step's conditions were met, so the workflow continued.

• Filtered — the step's conditions weren't met. The workflow stops there, unless you've set up a separate path for that case (a Yes/No branch), in which case it continues down that path instead.

• Ready — a paused step that's set to resume.

Run detail

Open any run to see:

• Entities — the orders, jobs, or deliveries the run touched, each linked so you can jump straight to it.

• Execution Steps — every step the run went through, in order, each with its own status.

Together these let you confirm a workflow did what you expected, or see exactly where it didn't.

Test vs Run

The workflow editor gives you two ways to try a workflow before you rely on it:

• Test runs it in dry-run mode — nothing it would normally do (send a notification, apply a strategy, and so on) actually happens. Testing a single step also offers an optional live-test toggle for cases like a message action, so you can send one real, clearly test-labeled message to confirm an integration works.

• Run is not a simulation — it executes the workflow end-to-end and fires any action it reaches. Use it once you're ready to see a workflow work for real, or to catch up orders it missed. See run a workflow manually for more.

Still building the workflow itself? See build a workflow.