Email notification for jobs that didn't start as expected - VisualCron - Forum

Community forum

tccl
  •  tccl
  • Paid support Topic Starter
2019-07-30T22:45:44Z
Hi there,

I have jobs that depends on both time and file triggers, which sends out success emails upon completion; we have also set error/failure email notifications for jobs that start and don't complete.

Is there a way to setup an email notification for jobs that are supposed to run at a certain time but do not trigger/start at all? We've had instances where we didn't realize a job didn't run until several hours later because the file wasn't received and thus the trigger didn't fire.


Any help would be much appreciated. Thank you in advance!
Support
2019-07-31T08:21:08Z
Originally Posted by: tccl 

Hi there,

I have jobs that depends on both time and file triggers, which sends out success emails upon completion; we have also set error/failure email notifications for jobs that start and don't complete.

Is there a way to setup an email notification for jobs that are supposed to run at a certain time but do not trigger/start at all? We've had instances where we didn't realize a job didn't run until several hours later because the file wasn't received and thus the trigger didn't fire.


Any help would be much appreciated. Thank you in advance!



Hi,

I moved your topic to "Feature requests" as we currently do not support this feature. Could you explain a little more in depth how you'd like this function to work. Like, if you have any suggestion or idea we can pass on to the developers on what the feature would react to when triggering that the "job isnt started", if you understand what I mean.
Michael
Support
http://www.visualcron.com 

Please like  VisualCron on facebook!
al355
2019-08-09T10:48:48Z
The way we deal with this is to have a separate error handler job which has a time trigger. So for example if no file was received by 16:30 then that trigger fires. The second job's trigger is disabled if the first one is successful and is re-enabled at the start of every day.
tccl
  •  tccl
  • Paid support Topic Starter
2019-08-09T15:14:28Z
Originally Posted by: al355 

The way we deal with this is to have a separate error handler job which has a time trigger. So for example if no file was received by 16:30 then that trigger fires. The second job's trigger is disabled if the first one is successful and is re-enabled at the start of every day.



Thanks for the reply! Does this mean that if we have 20 primary jobs where we want to be notified if a file trigger doesn't arrive, we have to setup 20 separate, secondary jobs that will handle the errors? Or do you mean that each of the 20 primary jobs will have a task-handling error that is nested within each job?

Sorry for the trouble. I'd just like to clarify. Thanks again!
al355
2019-08-09T15:53:53Z
The way we do it would mean you have 20 secondary jobs that handle the errors.
d32
2019-08-09T18:14:11Z
The way we handle our miss jobs is through variables and conditions. Say a variable whose value is a date. The job that is suppose to run (say when the file arrives) will also change the variable to today's date. Then a separate job runs with a time trigger and a condition to check if the variable is today's date, and if not then send an email saying the job is missed.

Ideally it would be nice to have VC have this type of check built in.
Scroll to Top