Sometimes a workflow may not run as expected, meaning emails, SMS, or other automated actions are not triggered. This usually happens when filters or conditions are not set up correctly. Understanding how triggers and filters work is key to ensuring workflows behave as intended.
Common reasons why workflows do not run
Filters are incorrectly set up
Filters determine when and how a workflow will run. If they are not correctly applied, the workflow may never be triggered.
What to check:
Review your filter logic to ensure it still applies to your business case.
Make sure that conditions do not contradict each other.
Triggers and filters don’t align
Workflows are triggered by events (e.g., New Invoice Created). If the filters attached to that trigger cannot logically be true, the workflow will not run.
For example:
If you use New Invoice Created as the trigger, you cannot filter for payment statuses like Paid or Payment Scheduled, since an invoice is never created.
Timing of conditions
Filters apply every time a workflow step is executed. This means that if a customer or invoice does not meet the condition at that specific point in time, the workflow will not run.
What to check:
Ensure that conditions are not too restrictive.
Consider whether the customer attributes (e.g., overdue days, contact details) are available at the step where the workflow runs.
Restrictive Workflow Filter:
