This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
I utilize the Workflow Events quite a bit, but the standard options fall short in a few critical cases.
For example: I use the events to send me an email after the workflow runs with errors.
Usually that is all I need. But, I have run into a few situations where the workflow didn't run at all - thus, no email was sent.
One such instance was on our server. While still initializing (before it even hit tool #1) the job hung. It sat like that for over a day before I noticed that there were no jobs running through a particular worker at all and saw this one sitting there.
A second such instance was recently when I changed Persistence Options and accidentally deleted the source for a scheduled job. The workflow marked itself complete in the scheduler and gave an error message of "Corrupt: Internal Error in PersistenceContainer......"
I realize that these are unexpected events and application errors (which I've worked with support on); but it would add great value to have that fallback mechanism to let us know the error happened.
Understandably, it would probably take a lot of work to engineer a schedule monitor that would catch this - but I think it would be worthwhile.
One option to do this: have an Event to email or run a command if a workflow hasn't started within a certain grace period after its scheduled time.