You are viewing limited content. For full access, please sign in.

Question

Question

Delay vs workflow that runs on a schedule

asked on April 15, 2021

So, I have a process that I want an automatic check on a status every 30 days, but each process may come in at any time so if I use a delay, I could have like 200 processes running.  Should I use a separate workflow that would run daily and look for each instance.

I am invoicing customers, and I want to check daily to see if the invoice is over 30 days old.

0 0

Answer

SELECTED ANSWER
replied on April 15, 2021

Hi Katy,

In a scenario like that, I would typically use a single scheduled workflow, and I would set it to single instance mode so no more than one instance could ever run at a time.

Delays aren't necessarily a problem, but I usually only go that route if I have a small number of active instances and the delay is relatively short.

Another advantage of the schedule is if something "catastrophic" happens, you don't have to worry about a bunch of "waiting" instances, the scheduled process would just run when things are resolved.

3 0
replied on April 16, 2021

Yes indeed, everything Jason said but especially this:

Another advantage of the schedule is if something "catastrophic" happens, you don't have to worry about a bunch of "waiting" instances, the scheduled process would just run when things are resolved.

1 0
replied on April 19, 2021

Thank you both for your input.  I have decided to create a workflow that will run daily, early in the morning .  It is just a quick workflow that has a custom query that searches for dates older than 30 days with a balance greater than zero and for each row sends an email to (someone), that states that the invoice is older than 30 days and not paid yet.  This, in the future, may trigger an automatic invoice with a late fee on it, but for now it is just a notification.

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.