Hi.
Quick question:
I found a someone else's construct in our Process Monitoring and the active instances of it keep piling up. It looks like this:
JOBP (ENDED_OK)
|----------- Child 1, some SAP Job (ENDED_OK)
|----------- Child 2, some SAP Job (ENDED_NOT_OK)
|----------- Child 1, some SAP Job (ENDED_OK)
- I understand that it's one of the idiosyncrasies of Automic that JOBP by default can be ENDED_OK even if some of their children are ENDED_NOT_OK (I think it's silly, but that's me)
- I also understand that JOBP don't deactivate until all their children deactivate - fair enough
But here's what I don't get:
Both the JOBP, and also all of the children, are configured "Deactive: always" in their attribute tab! Does anyone know why Child 2 and the JOBP then didn't deactivate by themselves?
Is this a bug, or another idiosyncrasy?
Thanks!