Automic Workload Automation

  • 1.  Event Notifications on Failure Not Working

    Posted Oct 12, 2018 09:55 AM

    Good Morning,

     

    We are working on improving some of our notifications for objects, and are having a hard time with Events.  For example, the event will be out in Activities and will run at each interval, however, if one of the executions fails, we are not receiving notifications.

    We have tried using the Runtime tab which works on other objects (JOBS, JOBP), but let's say there is an access denied error during a few of the executions, we need to know.  Another example, is if there are some variables defined and perhaps there is an error there, each Event execution will fail, however, it will not notify anyone.  The only way to see this is to go to the Statistics for that Event, and then Child Task Statistics, which is lots of clicking and can get a bit confusing. Other than adding code in to each Event, is there a better way to do this?  Ideally we would like to use the available functionality and not do too many random customizations.

    Please let me know if anyone has a good solutions for receiving notifications on Event objects.

    Thanks!

    Tina



  • 2.  Re: Event Notifications on Failure Not Working

    Posted Oct 12, 2018 11:29 AM

    We rarely use event objects, so we haven't experienced the issue you have described. 

     

     

    Do these faults get reported to the message log?   We do additional error handling here based upon pulling unexpected errors off of the message log. (table=MELD)



  • 3.  Re: Event Notifications on Failure Not Working

    Posted Oct 15, 2018 03:07 PM

    Hi Pete,

     

    We use them for certain executions and they've been running well so far.  They are typically not critical ones, so in the event one doesn't start, it will generally run again later on.

     

    I'd have to dig through the logs to get the exact errors that we see, that might be helpful for us.  We tried to change the status to shoot us out a notification, but unfortunately that wasn't working as expected.

     

    The main thing we're looking to change are the flag file workflows that need to execute very frequently during the day.  We're testing using a File Event instead which does work, but if it can't trap the errors then we have to look at a different way to get around it.  



  • 4.  Re: Event Notifications on Failure Not Working

    Posted Oct 16, 2018 03:04 PM

    Hi

     

    we do not use EVNT objects heavily too...

     

    if one of the executions fails, we are not receiving notifications.

    => why not?

     

    how does your !EVNT usually look like? - possibly you can add an include to check the execution. if you use ACTIVATE_UC_OBJECT you can quite easily implement a basich execution check...

     

    cheers, Wolfgang



  • 5.  Re: Event Notifications on Failure Not Working

    Posted Oct 17, 2018 12:12 PM

    Hello,

    So for us, in the !EVNT it might show FAULT_OTHER - Start impossible. Other Error.  At this point, we don't receive a notification and the Event will just continue to execute on its' normal schedule.  If i look at the Details of the failure, it shows the Return Code as 0, and normally with a Fault it would be another status which would then generate a runtime error.

     

    One time, we had a user that had left the company but there was an event still running under their ID.  This never produced an error message, but the Event kept running.  It was the same symptom as above where it was FAULT_OTHER and since the return code was 0, there were no notifications sent out.  In this case, it doesn't look like the Runtime is processing as the result is 0.

     

    We'll do some more testing with ACTIVATE_UC_OBJECT to at least get the right failure on that part.

     

    Thanks!!



  • 6.  Re: Event Notifications on Failure Not Working

    Posted Oct 18, 2018 09:05 AM

    TinaHart609265 schrieb:

     in the !EVNT it might show FAULT_OTHER - Start impossible. Other Error.  At this point, we don't receive a notification

    Thats clear, FAULT_OTHER is a script error that stops processing of this script.

    I suppose a logical Error in your !SCRIPT - pls check it for any script errors.

     

    cheers, Wolfgang



  • 7.  Re: Event Notifications on Failure Not Working

    Posted Oct 18, 2018 03:10 PM

    Hello,

    For us, we've also come across the FAULT_OTHER error before with Access Denied.  In this case, the event was running just fine and then the user was either locked out or expired.  At that point, all consecutive events were failing with Access Denied, however, it did not fail the event or send out any notifications.  This is where we have the problem.

     

    For errors in the scripts, we ask that full testing is completed before starting any executions, but sometimes that has not happened.  At this point, if the extra validation is not done, then there is a failure as well.  I know that most of our events aren't critical so even if we wrote something that might advise us if something fails 'x' times in an hour perhaps, that might be helpful as well.  I know the MELD table is mentioned above, so we might have to look at that as well.