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.

Workflows is a beta feature; if you don't have it yet, reach out to Nash for early access.

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

Every run — and each step inside it — uses the same set of statuses, so what you see on a run's row in Execution History means the same thing when you open it and check an individual step:

• Running — still in progress.
• Paused — waiting before it continues (for example, ahead of a delayed action) — it picks back up on its own.
• Passed — completed; its conditions were met, so the workflow continued.
• Filtered — the conditions weren't met, so the workflow stopped there. This isn't a failure — it's the workflow correctly deciding this particular job didn't qualify, so nothing downstream should happen — 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 — queued to go.

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.