Job execution and Run Id is not recorded in AWI.

[Shashank Devadiga]

We have a job that restarts AWI every day. If it ends with a return code other than 0, it sends a notification email. The issue is that the failed job's execution isn't even recorded in AWI.

We received an email saying the job was aborted, along with a report. But when we checked in AWI, the job showed as completed normally at the scheduled time, with no errors. Also, the RunID in the email doesn't match the one in AWI - they are two different executions.

The report for the failed job shows a network error, but the notification object that should have triggered the email has no execution record either.

Has anyone come across this kind of issue before, where a failure is reported but there's no trace of it in AWI?

-------------------------------------------

[Mike Halliday]

If there isn't an execution record for the notification, then perhaps a different CALL object sent the message?  Perhaps the CALL was duplicated by someone and the message text was not updated, and another task has triggered it?

You also say that you have a RunId in the message you received that isn't the AWI restart job, which job does that correlate to?  Check it's setup and history.

-------------------------------------------