Abrupt stop in workflow execution

[Michael Pokraka]

'last week' sounds a bit long ago. Check whether there are _any_ entries for that day. Especially TRFC's aren't usually retained more than a couple of days.
SM13 update failures are also a possible culprit.
 
I've seem similar behaviour and almost all 'unexplained' phenomena like this have been traced back to a basis-type problem.
The technical term used here is a 'blip' which everyone seems to accept as a perfectly reasonable explanation for anything odd that hasn't happened before.
 
Cheers
Mike
 
On Wed, Oct 15, 2003 at 09:03:46AM -0400, Parag Joshi wrote:
> Hi Alon,
>
> Thanks for your input.
>
> Checked the short dumps for past few days(This had happened few days ago,
> last week), nothing under WF-Batch.
>
> Any other suggestion?
>
>
> >-- Original Message --
> >Date:         Tue, 14 Oct 2003 21:19:59 +0100
> >Reply-To:     SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
> >From:         Alon Raskin <araskin at 3i-consulting.com>
> >Subject: Re: Abrupt stop in workflow execution
> >To:           SAP-WUG at MITVMA.MIT.EDU
> >
> >
> >Did you check for short dumps by WF-BATCH?
> >
> >
> >
> >Alon Raskin
> >
> >3i-consulting Group
> >
> >e: araskin at 3i-consulting.com
> >
> >w: http://www.3i-consulting.com <http://www.3i-consulting.com/>
> >
> >
> >
> >-----Original Message-----
> >From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of Parag
> >Joshi
> >Sent: Tuesday, October 14, 2003 9:19 PM
> >To: SAP-WUG at MITVMA.MIT.EDU
> >Subject: Abrupt stop in workflow execution
> >
> >
> >
> >Folks,
> >
> >
> >
> >I had a unusual situation.
> >
> >
> >
> >Workflow execution suddenly stopped during runtime. System was supposed
> >
> >to create a dialog workitem and it didn't. Workflow graphical log shows
> >
> >that is  stopped just before creating the dialog workitem. No errors logged.
> >
> >I somehow re-started the workflow with "restart workflows after system
> >crash"
> >
> >and it started, though it ended in error after the dialog workitem was
> >executed.
> >
> > Then I used "restart after error" to get the workflow in track.
> >
> >
> >
> >Again, there was no system crash, everything was working perfectly fine.
> >
> >Workflow has been functional for long time, dialog task is a old recurring
> >
> >task. No authorizations were changed. Funnier part, I am not able to
> >recreate
> >
> >the situation. I am having hard time locating the culprit and convincing
> >
> >the users the it won't happen again.
> >
> >
> >
> >In my design, I am calling sub-workflows in loop, loops can eventually
> get
> >
> >quiet deep, typically 8 levels. I am not sure if this loops causes hiccups
> >
> >for the system to keep track of.
> >
> >
> >
> >
> >
> >I have never faced such situation before...anybody has?
> >
> >
> >
> >Thanks.
> >
> >Parag Joshi.
> >
> >SAP Workflow Consultant.