The Workflows list: run counter, failed runs, last trigger, duplicate and search
The Workflows screen shows at a glance how many times each one ran, how many failed, when it last fired, and lets you duplicate and search them.
The Workflows screen lists every flow in your workspace as cards, each with its own run stats, plus tools to search, filter, duplicate, and toggle active/inactive without opening the editor.
What each card shows
- Nodes: how many steps the workflow has.
- Runs: total historical executions.
- Failed: how many of those executions ended in error (highlighted in red when greater than zero).
- Success rate: a progress bar computed as (runs − failed) / runs, only shown once the workflow has run at least once.
- Last run: a relative "X ago" timestamp, or "Never executed" if it hasn't fired yet.
- A toggle to activate/deactivate the workflow without opening the editor.
Search and filters
- The Search field matches against the workflow's name or description.
- The Trigger filter narrows the list to workflows using one specific trigger (message received, contact created, tag added, etc.).
- The Status filter shows all / active only / inactive only.
- "Clear filters" resets all three at once.
Duplicating a workflow
The duplicate button creates a full copy (nodes and connections included) with these behaviors:
- The name becomes "Original name (copy)".
- The copy is created inactive — you have to activate it yourself.
- Stats (executions, last run) start at zero: the copy does not inherit the original's history.
Example
You have a "VIP Welcome" workflow that has run 340 times with 12 failures (96% success). You duplicate it to build a variant for another language: the copy, "VIP Welcome (copy)", shows up inactive with 0 runs, ready for you to edit its nodes without touching the original that's live in production.
Tips
- Combine the Trigger and Status filters to quickly find, say, every inactive workflow triggered by "Message received" that you might have forgotten to re-enable.
- If a workflow shows a high "Failed" count, open its editor and check that workflow's own execution history to see the error reason.
Troubleshooting
- If "Runs" is 0 and "Last run" says "Never executed", the workflow has never fired — confirm it's Active and that its trigger event is actually occurring.
- If you duplicated a workflow and don't see changes reflected on the original, that's expected: the two become fully independent workflows from the moment of the copy.
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.
-
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.
-
Ready-to-use workflow templates
Start your automations in minutes from prebuilt flows you can customize.