In general, failures you suggested might suggest a failure, except when retrying is involved. Ideally, workflow should send a workflow failed message, which is not happening AFAIK.
For a start, I think we should do a timeout based mechanism to mark any workflow that did not had an update for more than T time has failed. --Srinath On Sun, Jul 15, 2012 at 10:44 AM, Isuru Madushanka Weerarathna <[email protected]> wrote: > Hi All, > > We are interested in knowing which workflows have been successfully > completed and which haven't (with a failure). By looking at the schema [1],* > *'workflowTerminated' event message is the only one receives at the end of > a workflow (without saying a success or a failure). > > We want to know that how do we identify whether a workflow is terminated > due to a failure? I am assuming any of following failed event messages will > lead to the termination of workflow. > > - invokingServiceFailed > - sendingFault > - receivedFault > - sendingResponseFailed > > Is this explanation correct? > > > - [1] > > http://svn.apache.org/repos/asf/incubator/airavata/trunk/modules/commons/workflow-tracking/src/main/resources/schemas/workflow_tracking_types.xsd > > > -Regards > Isuru -- ============================ Srinath Perera, Ph.D. Senior Software Architect, WSO2 Inc. Visiting Faculty, University of Moratuwa Member, Apache Software Foundation Research Scientist, Lanka Software Foundation Blog: http://srinathsview.blogspot.com/ Photos: http://www.flickr.com/photos/hemapani/ Phone: 0772360902
