Hi Shashank,
I also believe that this is a bug. This may be due to the fact that the JSCH is assigned a new instance at the period change and the check is therefore not performed.
The only uncommon setting I can see at the moment is the unnecessary marked checkbox "Repeat" but I also do not believe that this is the cause.
May I suggest that you put the jobs into workflows and then do the results check there?
What version are you using?
Best regards,
Tim
------------------------------
Automation Evangelist
Fiducia & GAD IT AG
---
Mitglied des deutschsprachigen Automic-Anwendervereins FOKUS e.V.
Member of the German speaking Automic user association FOKUS e.V.
------------------------------
Original Message:
Sent: 10-21-2019 11:58 PM
From: Shashank Singh
Subject: Job Failure doesn't trigger notification when job run crosses to next day
Hi Prosenjit,
Yes the job runs long and actually fails. Status - ENDED_NOT_OK - aborted.
The Call Operator statistics also do not show the Call Alert generated which means the execution of the alert isn't happening.
I suspect this to be a bug unless someone can guide / point me to any missing configuration.
Regards,
Shashank Singh
Original Message:
Sent: 10-21-2019 10:40 AM
From: Prosenjit Maji
Subject: Job Failure doesn't trigger notification when job run crosses to next day
Hi Shashank,
The instance gets long runner that really gets "Abend" status next day ?
Or
It gets any other status like "Ended_empty" etc. ?
Did you check the call operator statistics ? Did that get execute by the given property and still you did not receive email ?
I am not sure on this because the behavior explained is not expected & so far not aware of such bugs.
------------------------------
Prosenjit
Original Message:
Sent: 10-21-2019 05:28 AM
From: Shashank Singh
Subject: Job Failure doesn't trigger notification when job run crosses to next day
Original Message:
Sent: 10-21-2019 05:17 AM
From: MAJI
Subject: Job Failure doesn't trigger notification when job run crosses to next day
Hi Shashank,
So far with the available information, I believe, you are not hitting into some 'known' generic issues as such.
Would you be able to post a 'Postcondition' properties screen for reference ?
------------------------------
Prosenjit
Original Message:
Sent: 10-21-2019 01:04 AM
From: Shashank Singh
Subject: Job Failure doesn't trigger notification when job run crosses to next day
Hi Tim,
Alert mechanism is implemented in Post-Conditions.
Job's task properties --> Post Conditions.
It is a normal standalone job (JOBS) directly scheduled via Schedules (JSCH).
Regards,
Shashank Singh
Original Message:
Sent: 10-21-2019 12:40 AM
From: Tim Quakulinsky
Subject: Job Failure doesn't trigger notification when job run crosses to next day
Hi,
there are several ways to send a notification in case of an error, e.g. post script, post conditions, successor in workflow, attributes tab of workflow, etc.
Can you please specify how it is implemented in your system?
Best regards
Tim
------------------------------
Automation Evangelist
Fiducia & GAD IT AG
---
Mitglied des deutschsprachigen Automic-Anwendervereins FOKUS e.V.
Member of the German speaking Automic user association FOKUS e.V.
Original Message:
Sent: 10-19-2019 02:01 PM
From: Shashank Singh
Subject: Job Failure doesn't trigger notification when job run crosses to next day
Hi All,
I have observed a strange thing that a call alert / notification isn't getting generated and triggered when the job activated on a day runs long and fails on another day. The job is configured to send a failure notification and it has sent the notification when the failure occurs on the same day. But when the job failure occurs on the next day of job activation it doesn't send an alert. Has anyone encountered such an issue? Any pointers to rectify such this issue will be helpful.
Regards,
Shashank Singh