Long delay in raising events

Edward Diehl edwarddiehl at hotmail.com
Mon Oct 21 14:56:07 EDT 2013


We are testing EHP6 and have a workflow where BUS1065.REHIRED is followed by BUS1065.POSITIONCHANGED, all on the same object instance.  This is as it should be.  The workflow has a step that checks for a running instance of REHIRED.  If found it cancels itself as it is not needed.

We have a couple of instances where the POSITIONCHANGED event is not being raised until after the REHIRED workflow has completed and thus does not cancel itself.

We have an instance where the POSITIONCHANGED event follows a full 20 seconds after the REHIRED event.

Has anyone seen such behavior?   Any suggestions as to what needs to checked/changed?

Thanks all.

Ed

Ed Diehl
"Success consists of going from failure to failure without loss of enthusiasm." 

 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20131021/6200b570/attachment.htm


More information about the SAP-WUG mailing list