AnsweredAssumed Answered

v9 - problems having schedule trigger objects for non-OK tasks?

Question asked by Daryl_Brown_218 on Nov 7, 2014
Latest reply on Dec 30, 2014 by Jeremy_Swartwood_269
We have all of our schedules configured to fire a SCHED_FAILURE_ALARM notification object if any of its tasks end in something other than ANY_OK.  (This is configured on the schedule's attributes tab under the 'Result evaluation per task' section at the bottom.)

We recently went live with automation for a new customer, complete with a new schedule object, and due to having failed to promote a particular include object (my bad), one of my scheduled workflows blew up with a "FAULT_OTHER - Start Impossible" error.  The weird thing here was that the schedule did NOT kick off the SCHED_FAILURE_ALARM like it should have.  I've filed INC0329876 with Support about this one, and they're asking me to turn on tracing and reproduce the error.

To this point, I haven't figured out how to reproduce the error, so I'm stuck.

Has anyone else experienced this problem at all, or know how to reproduce it?

Outcomes