I have a workflow that should be triggered by a saved search... is there any way to determine that? (it is a dunning workflow that auto emails if the customer is late by x amount of days) -- but I am running into an issue where it the workflow doesn't seem to execute the saved search. what am I missing here?

Feel free to share your workflow setup with screenshots - but this is one of those things that can be hard to diagnose.

I know that it kinda works... a customer got a 85 and 90 day overdue notice, but none of the 3 other ones... my theory is that the main saved search isn't being run often enough. when I look at the execution log of the workflow, the only executions are ones that I have made. My assumption is that the workflow's schedule isn't working

Any reason you can't consolidate your different stages and just use an action with a condition in a single stage?

@KevinJ of Kansas this was setup by another company for us... I'll have to look at seeing how an action would be setup. the transitions are all tied to saved searches with "days overdue" criteria

you'd need to set up multiple actions in one transition.

hmm one issue it seems that doing a action route would be is that you can't really follow a trail of if they were sent 14 day vs 30 day notices... since a workflow would just say "first state name" --- though today I see that 3/5 customers were emailed their 14 day notice...

I wouldn't sweat it.

the multiple action route sounds like it might be the better way to go.... looks like set notice doesn't exit if the customer pays between the 14 day and 30 day etc window.... I will try the action route and see how that works

It really shouldn't matter