Job Groups & FAULT_OTHER activations

Discussion created by joel_wiesmann_automic on Jan 6, 2016
Latest reply on Jan 8, 2016 by joel_wiesmann_automic
Hi there
If you have an object attached to a job group, it can be activated (ACTIVATE_UC_OBJECT) and it will be visible in status registered. Once the job group starts, the object will generate. However if the object can not properly generate and ends up with an FAULT_OTHER, the object's runid will NOT show up in the JOBG report nor will it have the JOBG as a parent. The JOBG will not notice at all, that one of the "triggered" objects failed.

Anyone had the same issue and knows a workaround? I at least want to know about the failed job.