Abrupt stop in workflow execution

Becker, Stephan stephan_becker.ext at siemens.com
Wed Oct 15 10:40:14 EDT 2003


You misread my mail below, I quoted transaction SM58, not 38!
 
-----Mensaje original-----
De: Parag Joshi [mailto:parag at sra3s.com]
Enviado el: 15 October 2003 16:33
Para: SAP-WUG at MITVMA.MIT.EDU
Asunto: Re: Abrupt stop in workflow execution
 
Stephan,
 
SM38 does not have user selection, I am on 6.20. It is a "Queue
Display/Maintain"
transaction.
 
Please check.
 
Thanks,
Parag Joshi.
 
>-- Original Message --
>Date:         Wed, 15 Oct 2003 15:05:42 +0200
>Reply-To:     SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>From:         "Becker, Stephan" <stephan_becker.ext at siemens.com>
>Subject: Re: Abrupt stop in workflow execution
>To:           SAP-WUG at MITVMA.MIT.EDU
>
>
>Hi Joshi,
>
>Make sure you deselect your own user in the selection screen on sm58, and
>select the right date range..
>
>Greetings,
>Stephan
>
>-----Mensaje original-----
>De: Parag Joshi [mailto:parag at sra3s.com]
>Enviado el: 15 October 2003 15:01
>Para: SAP-WUG at MITVMA.MIT.EDU
>Asunto: Re: Abrupt stop in workflow execution
>
>Hi Stephan,
>
>Thanks for your input.
>
>This had happened few days ago last week, so I am checking the system
>logs/traces
>pertaining to that date.
>
>I checked SM38 -> "No queues to display".
>Transactional RFC log -> "Nothing was selected".
>
>
>
>>-- Original Message --
>>Date:         Tue, 14 Oct 2003 22:25:49 +0200
>>Reply-To:     SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>>From:         "Becker, Stephan" <stephan_becker.ext at siemens.com>
>>Subject: Re: Abrupt stop in workflow execution
>>To:           SAP-WUG at MITVMA.MIT.EDU
>>
>>
>>Joshi,
>>
>>Check the RFC log (sm58) and see if there was a temporary RFC layer
>overload
>>or something funny like that..
>>
>>Cheers,
>>Stephan
>>
>>-----Mensaje original-----
>>De: Parag Joshi [mailto:parag at sra3s.com]
>>Enviado el: 14 October 2003 22:19
>>Para: SAP-WUG at MITVMA.MIT.EDU
>>Asunto: 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.
 


More information about the SAP-WUG mailing list