Testing workflows (test runner) and viewing execution logs
Use the test runner to execute a workflow step by step and check the Timeline and Trace to see logs and payloads for each node.
Watch this step in the video · Testing the workflow
Why test a workflow before turning it on
The test runner lets you execute a workflow in a controlled way so you can see, step by step, which nodes run, in what order and with what result, without waiting for the real event to happen. It's the fastest way to spot a wrong condition, an empty variable or a branch that never gets taken.
Launching a test
- Open Workflows from the side menu and enter your workflow.
- In the toolbar click Test. The Test workflow dialog opens.
- Depending on the trigger, pick the context:
- Conversation or contact triggers ask for a reference conversation or contact. Use the search box to pick a recent one (no need to memorize IDs).
- Synthetic triggers (for example template approved/rejected, channel disconnected) show a Trigger data form to fill in the event values.
- Click the button to launch the run.
There are two modes depending on the trigger:
- Synthetic fire: the engine runs the workflow right away with the context you provided. Useful for triggers that have no real-time counterpart.
- Arm / listen: the workflow waits for the next real event (for example, the next inbound message) and fires when it happens.
Following the run live
When you launch the test, the dialog closes and two elements appear over the canvas:
- A floating status chip that shows whether the run is armed, running, waiting, completed, failed or cancelled. From there you can click View details / View results.
- The Timeline panel at the bottom of the canvas, with one pill per step: node name, status (✓ completed, ✕ failed, • skipped, ⏳ waiting, ⏱ delay) and duration. Click a pill to center that node on the canvas.
If a run stays waiting (because of a Delay, Wait or Ask question node), you can Stop it from the chip.
Reviewing previous runs: the History
- In the editor's top bar click History. Recent runs opens.
- Filter if needed: Status (All, Failed, Finished OK, Running or waiting, Cancelled), Workflow (This workflow or All workflows in the workspace) and From / To. Clear filters brings back the full view.
- Select a run to see its steps, with status and duration; if it failed, the error shows on the exact step.
- On a failed run, after fixing the cause, click Retry: it runs the whole workflow again with the same trigger data and the current version. Careful: steps that had already succeeded are repeated.
Details in Run history: filters and Retry.
If it doesn't work
- I can't launch the test: make sure the workflow is saved and the trigger has the required context (conversation or contact). The button is disabled while another test run is in flight.
- The run stays "armed" and never fires: in listen mode it's waiting for the real event; generate that event (for example send an inbound message to the channel) or switch to a synthetic fire.
- A node shows as skipped (•): its condition wasn't met. Open the step in the History to see the values it was evaluated with.
- A step fails (✕): open its payload to read the error; it's usually an empty variable or an HTTP call that returned an error.
Tip: test with a synthetic fire first to validate the logic, and only then use listen mode to confirm the real event comes in the way you expect.
Tip: the History keeps the latest 50 runs; use it as a log to compare before/after a change.
Related articles
Related articles
-
Build your first workflow
Omnifox workflows automate your operation: a trigger starts the automation and action nodes do the work. Build a welcome message in minutes.
-
Workflow triggers catalog
Learn which events can start a workflow automatically in Omnifox.
-
Workflows complete guide
Workflows in depth, in 54 chapters: triggers, nodes, variables, testing, history, templates, import and export, with every setting explained and a real workflow end to end.
-
Action nodes available in workflows
Discover the actions a workflow can run automatically.
-
Conditions and branching (if/then) in a workflow
Make your flows take decisions and follow different paths based on each contact data.