Run a workflow manually

Last updated: August 4, 2026

You don't have to wait for a trigger to fire to see what a workflow does. Nash can run one on demand against orders you choose — useful for catching up orders a workflow missed, or for firing a single real execution while you're still building it, before you turn it on for everything else.

Run it against a batch of orders

From the Orders list, select the orders you want, then choose Run Workflow. Pick one of your active workflows and run it — each selected order starts its own execution. This is the fast path for backfills: if you just activated a workflow, run it against the orders that came in before it went live.

Only active workflows are offered here, since this path is for applying a workflow you've already turned on to more orders — not for testing one that isn't live yet.

Test a single order before activating

To try a workflow you're still building, open the workflow itself and use Run Workflow there, providing an order or job ID. This fires one real execution against that order right now, so you can check a change works before activating the workflow for everything else.

Either way this isn't a simulation — it's a real run, so any actions the workflow reaches actually happen.

What happens next

Each manual run kicks off a normal execution — whatever the workflow does (apply a strategy, send a notification, tag the order, and more) happens just as it would automatically. See check the results in execution history to confirm it ran the way you expected.

Still putting the workflow together? See build a workflow for triggers, conditions, and actions.