This alert highlights that a workflow is filtering invoices based on a specific field and value, which may cause unexpected behavior when applied at the customer level.
Using the equals filter is extremely specific. We would recommend a greater than or equal to filter or less than or equal to filter instead. This can help with the margin of error factor.
An example of an equals filter issue would be, if the criteria met exactly 7 days but the 7th day landed on a weekend (Saturday or Sunday). Unless the button in your workflow settings "Send communication on weekends" was ticked, the workflow will not work, because the filter did not meet that exact requirement.
Let's say this was a coming due workflow. Therefore, the workflow would fail to send and only resend the following month (assuming it did not fall on a weekend again).
This could result in certain invoices being included or excluded incorrectly, potentially impacting automation outcomes.
Workflow has a filter for invoices with days_overdue equals 5 which may lead to unexpected behaviour for a Customer level workflow.
Next Actions:
Review the filter criteria to ensure it aligns with the intended workflow logic.
Check affected customers and invoices to identify any unintended exclusions or inclusions.
Adjust workflow settings if necessary to better match customer-level automation requirements. Such as changing the filter from equals to greater than or quals to or less than or equals to.
We've given this Due Workflow a 7 day criteria by adding a high and low criteria in my filters.
If you would like this customer to receive only one reminder email when they reach -7 days overdue (also known as 7 days before due) and you do not wish for the customer to meet the criteria again the following day and receive another email, change the workflow restart Settings to something like the number in the filter (7). Because if the Settings we set to 1 day before restarting, in theory, this customer would receive 7 emails, one per day for 7 days (unless they make the payment and they no longer meet the workflow requirements).
